[RFC PATCH 0/4] Introduce global.bootm.root env var for booting via PARTUUID

[Robert Karszniewicz <r.karszniewicz@phytec.de>]

This patch introduces a new env var which specifies which device
is the rootfs device to be used in Linux, passed to Linux via bootargs,
identified by the rootfs partition's PARTUUID.

global.bootm.root supplements global.bootm.appendroot, in that it overrides
appendroot's naïve default, which picks the partition that the kernel resides
on (global.bootm.image).

I don't know if it is the right way, or a good way, but this is the shortest
and simplest way that I've found.

What do you think of this? And is it generally something that would be
accepted, or is this out of scope for barebox?

Example:
detect mmc2
global.bootm.image='/mnt/mmc2.0/zImage'
global.bootm.appendroot=1
global.bootm.root='/mnt/mmc2.1/'
boot mmc

Note that the trailing slash is important.
See comment in follow_automount() in fs/fs.c

Robert Karszniewicz (4):
  bootm: add env var root_dev
  globalvar: add bootm.root
  bootm: handle global.bootm.root
  bootm: mount root device before accessing linux_rootarg

 common/bootm.c  | 13 +++++++++++--
 include/bootm.h |  2 ++
 2 files changed, 13 insertions(+), 2 deletions(-)

-- 
2.7.4


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