mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 00/11] ARM: at91: sama5d4: add basic Wifx L1 support
Date: Wed, 28 Dec 2022 11:46:30 +0100	[thread overview]
Message-ID: <Y6wehj862Z+p/3f/@ravnborg.org> (raw)
In-Reply-To: <4b535e4b-688c-4837-4953-4de558c8cd1d@pengutronix.de>

Hi Ahmad.

> I have also resynced the Atmel NAND driver with
> Linux to get support for the new EBI binding, but I'll send that out
> as a separate patch once this is in. (If you need it for your hacking,
> I can push it somewhere before that though).
No need for the new EBI binding atm, so no reason to rush it.

> 
> > The DT file in patch 11 looks like a file that would be a good linux
> > kernel candidate - but I guess this is for someone else to do.
> 
> It's on the bucket list, but first barebox, DistroKit and then eventually
> upstreaming the kernel DT.
Hopefully there is a fist stage bootloader somewhere in the todo list.
I really like how this works with PBL and multi image - it is very elegant
in barebox and then at91bootstrap is no longer required.

> > I look forward to the day where the remaining three sama5d boards are all
> > multi-board and DT-enabled. This patch-set brings us a step closer.
> 
> I don't have the boards, that are not yet DT-enabled, but I guess due
> diligence is done if we verify that the DT-enabled drivers work on some
> other SAMA5 board, which already has DT support. Now, with the NAND
> driver I ported for this, there remain three drivers that I have so
> far not tested:
> 
> LCD, PWM and USB (Both Host/Gadget).
> 
> If you tell me, that all these already work just fine for some SAMA5 with
> DT (or that they didn't work at all for SAMA5 without DT), I can send the
> patch series switching the remaining boards to multi-image.

I have a sama5d4 eXplained board - but the display no longer works.
I will try to take a look at DT enabling the board if I find time.
We can revisit what to do then, if you do not beat me to it before.

> 
> > Do you know if there is a way to read bootsource from an at91sam92XX
> > CPU / ROMBOOT code?
> 
> I just observed that the info is in r4 on all SAMA5 SoCs. Maybe that's
> the case for the older SoCs too?
Looking at at91bootstrap I do not have high hopes.
Only the sama5 chips have this code enabled.
(Looked at v3.9.3 - which is the latest with at91sam9x support).

	Sam



  reply	other threads:[~2022-12-28 10:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 10:58 Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 01/11] ARM: at91: sama5: switch to nonnaked entry functions Ahmad Fatoum
2022-12-16  6:49   ` Sascha Hauer
2022-12-14 10:58 ` [PATCH 02/11] ARM: at91: sama5d4: add entry point helpers Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 03/11] ARM: at91: sama5d4: enable for DT use Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 04/11] net: macb: match atmel,sama5d4-gem compatible Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 05/11] i2c: at91: extend for SAMA5D4 support Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 06/11] eeprom: at24: add 24mac402/602 support Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 07/11] driver: always ensure probe of RAM registered with mem_platform_driver Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 08/11] common: deep-probe: don't build without CONFIG_OFDEVICE Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 09/11] pinctrl: at91: make deep-probe compatible Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 10/11] ARM: at91: make bootsource code generic to all SAMA5 Ahmad Fatoum
2022-12-14 10:58 ` [PATCH 11/11] ARM: at91: SAMA5D4: add Wifx L1 support Ahmad Fatoum
2022-12-27 10:26 ` [PATCH 00/11] ARM: at91: sama5d4: add basic " Sam Ravnborg
2022-12-27 20:40   ` Ahmad Fatoum
2022-12-28 10:46     ` Sam Ravnborg [this message]
2022-12-28 11:13       ` Ahmad Fatoum

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=Y6wehj862Z+p/3f/@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