From: Sam Ravnborg <sam@ravnborg.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Date: Tue, 11 Jan 2022 23:12:39 +0100 [thread overview]
Message-ID: <Yd4A12htShfcvl6+@ravnborg.org> (raw)
In-Reply-To: <d8f67d11-e18d-0bb5-ec76-b8bbfce75add@pengutronix.de>
Hi Ahmad,
> > I have the code locally - but this time I will not have it posted before
> > it is tested.
> >
> > Then I cloned the latest at91bootstrap - but they no longer support old
> > at91sam92xx CPUs.
> > So it was time to enable bootstrap support for at91sam9263.
> >
> > In the past I had something working, but alas no luck this time.
> >
> > Can anyone (Ahmad?) help me a little how to get the bootstrap
> > functionality working on the at91sam9263?
> >
> > I do not expect patches, but I hope for something that can point me in
> > the right way to do it.
> >
> > I have skov-arm9cpu boards (plenty - as they are mostly retired by SKOV)
> > and one at91sam9263ek where I can test.
>
> The skov-arm9cpu looks like it already runs first stage without at91bootstrap?
> So the issue is only with at91sam9263ek?
For the moment my focus is on the skov-arm9cpu - and here bootstrap is
not (yet) functional. But I think with all the good feedback from you
and Oleksij I should manage. Thanks for the replies!
> > We see very little interest in at91sam92* boards and we could decide
> > to retire all the boards that are not updated to multi-image.
>
> As long as it works, I guess most people don't see a reason make interest
> publicly known.
>
> > This could simplify things - and if there is interest the missing boards
> > can be brought back to life provided they are updated to multi image.
> > Any comments on this?
>
> I have only worked on SAMA5D3 and SAMA5D2. Of course, I'd like to see
> board code in AT91 replaced with DT-enabled/multi-image-compatible code,
> but I don't think it will happen. I don't think the maintenance burden
> is high, so I'd just leave it as is. If it bitrots and people complain,
> we can nudge them into the right direction.
OK, you are right that if it just works no reason to touch it.
I will do the patches alongside the current codebase then.
Sam
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2022-01-11 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 18:38 Sam Ravnborg
2022-01-09 19:53 ` Sam Ravnborg
2022-01-10 5:33 ` Oleksij Rempel
2022-01-10 20:52 ` Sam Ravnborg
2022-01-11 8:08 ` Ahmad Fatoum
2022-01-11 7:57 ` Ahmad Fatoum
2022-01-11 22:12 ` Sam Ravnborg [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=Yd4A12htShfcvl6+@ravnborg.org \
--to=sam@ravnborg.org \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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