mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: i.MX: add barebox,bootsource-mmc aliases
Date: Tue, 20 Feb 2024 11:44:40 +0100	[thread overview]
Message-ID: <ZdSCmKtO_7higenQ@pengutronix.de> (raw)
In-Reply-To: <7a843e63-edb5-4a5c-b1f3-49a98e4e1f7a@pengutronix.de>

On Tue, Feb 20, 2024 at 10:12:47AM +0100, Ahmad Fatoum wrote:
> On 20.02.24 10:08, Ahmad Fatoum wrote:
> > Hello Sascha,
> > 
> > On 20.02.24 08:13, Sascha Hauer wrote:
> >> Several boards overwrite the standard mmc aliases to give them a board
> >> specific numbering. This breaks our assumption that the bootsource
> >> instance number matches the mmc alias numbering. barebox supports
> >> barebox,bootsource-mmc aliases to provide a mapping between the
> >> bootsource and the device nodes that provides them. Add these aliases
> >> for the newer i.MX SoCs.
> > 
> > Does this have an effect without i.MX calling bootsource_set_raw?
> 
> Typo: without it calling bootsource_set (it calls bootsource_set_raw)
> currently.

Indeed, I missed this. Sent v2.

Sascha

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



      reply	other threads:[~2024-02-20 10:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20  7:13 Sascha Hauer
2024-02-20  9:08 ` Ahmad Fatoum
2024-02-20  9:12   ` Ahmad Fatoum
2024-02-20 10:44     ` Sascha Hauer [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=ZdSCmKtO_7higenQ@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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