From: robin <robin@protonic.nl>
To: "Enrico Jörns" <ejo@pengutronix.de>
Cc: barebox@lists.infradead.org, david@protonic.nl
Subject: Re: Using bootspec with RAUC and redundant partitions
Date: Wed, 30 Sep 2020 15:18:39 +0200 [thread overview]
Message-ID: <2345573d89ba39fcb96a2d182ff3e5aa@protonic.nl> (raw)
In-Reply-To: <a447a82ae7f8e45a9e86b39d1aa0383504f1cf75.camel@pengutronix.de>
On 2020-09-30 13:48, Enrico Jörns wrote:
> Hi Robin,
>
> Am Mittwoch, den 30.09.2020, 13:26 +0200 schrieb robin:
>> Enrico,
>>
>> > On 2020-09-30 10:09, Enrico Jörns wrote:
>> > > Hi Robin,
>> ..
>> > > Why this would work anyway is because barebox extends the kernel
>> > > commandline with the root= entries required to boot the kernel from
>> > > that specific partition where it did read the entry from.
>>
>> Re-reading this, do you mean that the blspec files on the rootfs
>> partitions
>> should contain a root=/dev/mmcblk* of the partition they are on? And
>> thus
>> still contain dynamic (install time computed) configuration?
>
> no, what I meant was the opposite: To exclude this information from the
> blspec file.
ack, than we're on the same page here ;)
>> If I use 'boot /mnt/mmc2.4/boot' barebox finds the spec, kernel and
>> dtb
>> but my root= is not set in the kernel commandline.
>
> A little detail I forgot to mention is that barebox requires you to
> have a line 'linux-appendroot true' in the blspec file.
Thats what I missed. A custom bootspec key :P
blspec: booting vicut1-1.05.88.2.1 from mmc2
Adding "root=PARTUUID=f340a0f5-05" to Kernel commandline
Now works as previously discussed, thanks!
Best regards,
Robin van der Gracht
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2020-09-30 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 13:02 robin
2020-09-30 7:39 ` Sascha Hauer
2020-09-30 8:09 ` Enrico Jörns
2020-09-30 9:19 ` robin
2020-09-30 10:50 ` Robert Karszniewicz
2020-09-30 11:26 ` robin
2020-09-30 11:48 ` Enrico Jörns
2020-09-30 13:18 ` robin [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=2345573d89ba39fcb96a2d182ff3e5aa@protonic.nl \
--to=robin@protonic.nl \
--cc=barebox@lists.infradead.org \
--cc=david@protonic.nl \
--cc=ejo@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