mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>,
	Sascha Hauer <sha@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Boot from SD if SD-Card is present - Beaglebone Black
Date: Fri, 6 May 2022 14:20:04 +0200	[thread overview]
Message-ID: <4df2b2cc-8153-43f8-ee79-86f3423563d7@pengutronix.de> (raw)
In-Reply-To: <YnObAylvwzObEn+2@Hephaistos>

Hello Konstantin,

On 05.05.22 11:38, Konstantin Kletschke wrote:
> On Thu, May 05, 2022 at 10:25:07AM +0200, Sascha Hauer wrote:
> 
>> Several partitioning tools set this automatically, but not all it seems.
> 
> I got it. The partitions are created via sfdisk. No PARTUUID.
> 
> If I change the disk identifier with fdisk afterwards, the partitions
> magically also get PARTUUIDs. This can be scripted (by me):
> Something like
> fdisk /dev/mmcblk1 
> x
> i
> 0xaffedead
> r
> w
> 
> 
> Problem solved, with this the bootloader spec is working and I will
> implement that!

Great that you got it working. I'd still suggest that CONFIG_MMCBLKDEV_ROOTARG=y
be used for new projects with new kernels an with the same aliases hardcoded in
barebox and Linux. PARTUUID might be the best thing you can on x86 without
an initramfs, but we have device tree, so why not make use of that to
be absolutely sure bootloader and Linux address the same partition.

Cheers,
Ahmad

> 
> Regards
> Konsti
> 


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


  reply	other threads:[~2022-05-06 12:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 16:18 Konstantin Kletschke
2022-05-02  6:35 ` Ahmad Fatoum
2022-05-03 14:14   ` Konstantin Kletschke
2022-05-05  7:06     ` Sascha Hauer
2022-05-05  7:24       ` Konstantin Kletschke
2022-05-05  8:25         ` Sascha Hauer
2022-05-05  8:58           ` Konstantin Kletschke
2022-05-05  9:38           ` Konstantin Kletschke
2022-05-06 12:20             ` Ahmad Fatoum [this message]
2022-05-09  8:04               ` Konstantin Kletschke

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=4df2b2cc-8153-43f8-ee79-86f3423563d7@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=konstantin.kletschke@inside-m2m.de \
    --cc=sha@pengutronix.de \
    /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