mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Date: Tue, 11 Jan 2022 08:57:59 +0100	[thread overview]
Message-ID: <d8f67d11-e18d-0bb5-ec76-b8bbfce75add@pengutronix.de> (raw)
In-Reply-To: <Ydsrrj76kk6tmD2X@ravnborg.org>

Hello Sam,

On 09.01.22 19:38, Sam Ravnborg wrote:
> Hi all.
> 
> This little detour started because Ahmad pointed out I had made
> a stupid mistake in pwm-atmel.
> So I decided I wanted to give it a spin to verify if it actually works
> now.
> 
> The first challenge I encountered was that said driver had bit-rotted
> as it used the old pwm framework - so I updated it from the Linux
> kernel.

Ouch. How did I miss this :/

> 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?

> 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.

> I am happy to type the patches - and verify that the boards I have works.

Great. Looking forward to more boards in at91_multi_defconfig.

Cheers,
Ahmad

> 
> 	Sam
> 
> 


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  parent reply	other threads:[~2022-01-11  7:59 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 [this message]
2022-01-11 22:12   ` Sam Ravnborg

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=d8f67d11-e18d-0bb5-ec76-b8bbfce75add@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=sam@ravnborg.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