mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: robin <robin@protonic.nl>
To: robin@protonic.nl
Cc: barebox@lists.infradead.org, "Enrico Jörns" <ejo@pengutronix.de>,
	david@protonic.nl
Subject: Re: Using bootspec with RAUC and redundant partitions
Date: Wed, 30 Sep 2020 13:26:41 +0200	[thread overview]
Message-ID: <ec3d10ca7432771f49d1f4e14aaa5cae@protonic.nl> (raw)
In-Reply-To: <c88ecdbe8296e1e05b546115b2e3d21e@protonic.nl>

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?

I placed my kernel and bootspec entry in the rootfs partition under 
/boot.
The rootfs partition is mmcblk2p5 (barebox: mmc2.4).

The 'boot' command doesn't work with target 'mmc2.4' (probably since I 
placed
the data in a '/boot' subdirectory.

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.

Best regards,
Robin van der Gracht

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

  parent reply	other threads:[~2020-09-30 11:26 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 [this message]
2020-09-30 11:48         ` Enrico Jörns
2020-09-30 13:18           ` robin

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=ec3d10ca7432771f49d1f4e14aaa5cae@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