Re: root= kernel cmdline parameter

[Giorgio Dal Molin <giorgio.nicole@arcor.de>]

[-- Attachment #1.1.1: Type: text/plain, Size: 1427 bytes --]

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?
> 
> Best regards
> Uwe
> 
Hi,

thank you for answering.

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.

giorgio


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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