From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Giorgio Dal Molin <giorgio.nicole@arcor.de>
Cc: barebox@lists.infradead.org
Subject: Re: root= kernel cmdline parameter
Date: Mon, 6 Aug 2018 21:44:58 +0200 [thread overview]
Message-ID: <20180806194458.bdgb3uen4zclomlz@pengutronix.de> (raw)
In-Reply-To: <34f2c034-7f30-de15-93de-54f9a86e93a0@arcor.de>
Hello,
On Mon, Aug 06, 2018 at 09:30:30PM +0200, Giorgio Dal Molin wrote:
> On 08/06/2018 08:15 PM, Uwe Kleine-König wrote:
> > On Tue, Jul 31, 2018 at 01:20:12PM +0200, Giorgio Dal Molin wrote:
> >> Hi all,
> >>
> >> I'm trying to find out the best method to define the root=
> >> parameter when booting the linux kernel from barebox.
> >>
> >> My system boots from an sd card partitioned with a GPT.
> >> The sd card has two independent set of partitions with
> >> the following labels:
> >>
> >> 1) boot_1 + rootfs_1
> >> 2) boot_2 + rootfs_2
> >>
> >> for redondance in case one set gets damaged while updating.
> >>
> >> 'boot_1' is formatted with ext4 and contains the kernel + dtb images
> >> for the userland in 'rootfs_1'; and the same for 'boot_2' and 'rootfs_2'.
> >>
> >> Currently I hardcode the 'root' parameter to '/dev/mmcblk0p3' or
> >> '/dev/mmcblk0p4' corresponding to the kernel in 'boot_1' or
> >> 'boot_2' and it actually works but is there a better way to do
> >> this ?
> >>
> >> Using the global var. 'bootm.appendroot' does not work because the
> >> userland image is not in the same partition as the kernel.
> >
> > What is the blocker to put kernel and dtb in rootfs_X?
>
> I would like to keep kernel and userland separate to be flexible about
> how to pack the userland. The kernel supports more filesystems as the
> bootloader so I prefer to keep kernel+dtb in a small ext? partition and
> the rest in a separate part.
Is this a theoretical flexibility? i.e. do you use something for
rootfs_X that isn't supported in barebox? If no: You're making your life
unnecessary hard. If yes: why not teach barebox about it?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-08-06 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 11:20 Giorgio Dal Molin
2018-08-06 18:15 ` Uwe Kleine-König
2018-08-06 19:30 ` Giorgio Dal Molin
2018-08-06 19:44 ` Uwe Kleine-König [this message]
2018-08-08 7:52 ` Sascha Hauer
2018-08-09 7:45 ` Giorgio Dal Molin
2018-08-31 13:43 ` Giorgio Dal Molin
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=20180806194458.bdgb3uen4zclomlz@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=giorgio.nicole@arcor.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