From: Sam Ravnborg <sam@ravnborg.org>
To: Wolfram Sang <wsa@kernel.org>, Sascha Hauer <sha@pengutronix.de>,
barebox@lists.infradead.org
Subject: Re: [PATCH 0/3] mtd: nand: atmel: legacy: fix boot on USB-A9G20
Date: Tue, 21 Mar 2023 21:53:37 +0100 [thread overview]
Message-ID: <ZBoZUZaqUVwlxH/B@ravnborg.org> (raw)
In-Reply-To: <ZBn/ShAwKik7TdvZ@ravnborg.org>
Hi all.
Correcting myself here.
> >
> > Super interesting about the A9263 setup code. I missed it so far. Does
> > that mean that barebox can replace the at91bootstrap?
> Yes. The patch series I pointed at generates a bare variant that I
> successfully used to boot my board direct from ROMBOOT.
> It is a direct replacement for at91bootstrap and loads barebox as the
> next step bootloader.
The above is entirely correct - as the barebox variant supports booting from
SD card only, where at91bootstrap support additional boot sources.
Doable, but I did not have the need, so I did not look into it.
Sam
next prev parent reply other threads:[~2023-03-21 20:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 15:49 Wolfram Sang
2023-03-19 15:49 ` [PATCH 1/3] mtd: nand: atmel: legacy: add 'algo' to use Wolfram Sang
2023-03-19 15:49 ` [PATCH 2/3] mtd: nand: atmel: legacy: use proper ecc_shift Wolfram Sang
2023-03-19 15:49 ` [PATCH 3/3] mtd: nand: atmel: legacy: remove superfluous code Wolfram Sang
2023-03-19 18:51 ` [PATCH 0/3] mtd: nand: atmel: legacy: fix boot on USB-A9G20 Sam Ravnborg
2023-03-19 21:28 ` Wolfram Sang
2023-03-21 8:58 ` Sascha Hauer
2023-03-21 9:44 ` Alexander Dahl
2023-03-21 16:48 ` Sam Ravnborg
2023-03-21 17:20 ` Wolfram Sang
2023-03-21 19:02 ` Sam Ravnborg
2023-03-21 20:53 ` Sam Ravnborg [this message]
2023-03-21 21:42 ` Wolfram Sang
2023-03-22 7:37 ` Sascha Hauer
2023-04-27 17:25 ` Wolfram Sang
2023-04-27 17:26 ` Wolfram Sang
2023-03-22 7:41 ` Sascha Hauer
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=ZBoZUZaqUVwlxH/B@ravnborg.org \
--to=sam@ravnborg.org \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
--cc=wsa@kernel.org \
/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