From: Frank Wunderlich <frank-w@public-files.de>
To: Sascha Hauer <sha@pengutronix.de>,Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Ahmad Fatoum <ahmad@a3f.at>,barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Documentation: user: barebox: mention generic dt 2nd stage support
Date: Mon, 07 Feb 2022 10:36:42 +0100 [thread overview]
Message-ID: <5649171E-0BB6-4A39-AB3E-DAB262CDC50D@public-files.de> (raw)
In-Reply-To: <20220207083440.GD18637@pengutronix.de>
Am 7. Februar 2022 09:34:40 MEZ schrieb Sascha Hauer <sha@pengutronix.de>:
>On Mon, Feb 07, 2022 at 09:14:51AM +0100, Ahmad Fatoum wrote:
>> Hello Sascha,
>>
>> On 07.02.22 09:00, Sascha Hauer wrote:
>> > On Sun, Feb 06, 2022 at 12:19:30AM +0100, Ahmad Fatoum wrote:
>> >> Most users interested in chainloading barebox will probably want
>to use
>> >> the generic DT format for that: It will pass the checks the boot
>command
>> >> may have and it will ensure the system is in the correct state,
>e.g.
>> >> that caches are disabled.
>> >>
>example:
>> >> +
>> >> +.. code-block:: console
>> >> +
>> >> + U-Boot: tftp $kernel_addr barebox-dt-2nd.img
>> >> + U-Boot: tftp $fdt_addr my-board.dtb
>> >> + U-Boot: booti $kernel_addr - $fdt_addr
>> >> +
>> This is what the documentation is saying right now. It only appeared
>> in the diff, because I rephrased the start a bit. I don't have a
>> 32-bit ARM U-Boot here to test, so I'd rather not rewrite that part
>> myself.
>
>Well you've introduced the part to use the bootm command yourself :)
>
>commit 3a14fb79153af84323fee8308989011cd05c7d96
>Author: Ahmad Fatoum <a.fatoum@pengutronix.de>
>Date: Mon Jun 17 16:18:46 2019 +0200
>
>However, I obviously failed to review this properly. I'll create a
>patch
>for that.
>
>Sascha
In barebox "bootm flashable.img" works, in uboot it is booti with barebox-dt-2nd.img +fdt like example. I have a armhf bananapi r2 (mt7623),but it looks not supported by barebox
regards Frank
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2022-02-07 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 23:19 [PATCH 1/2] Documentation: remove some references to zbarebox.bin Ahmad Fatoum
2022-02-05 23:19 ` [PATCH 2/2] Documentation: user: barebox: mention generic dt 2nd stage support Ahmad Fatoum
2022-02-07 8:00 ` Sascha Hauer
2022-02-07 8:14 ` Ahmad Fatoum
2022-02-07 8:34 ` Sascha Hauer
2022-02-07 8:36 ` Ahmad Fatoum
2022-02-07 9:36 ` Frank Wunderlich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5649171E-0BB6-4A39-AB3E-DAB262CDC50D@public-files.de \
--to=frank-w@public-files.de \
--cc=a.fatoum@pengutronix.de \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox