diff options
author | Brian Norris <computersforpeace@gmail.com> | 2023-01-24 22:42:07 -0800 |
---|---|---|
committer | Christian Marangi <ansuelsmth@gmail.com> | 2023-02-04 20:16:20 +0100 |
commit | b5193291bdde00e91c58e59029d5c68b0bc605db (patch) | |
tree | 8bc332ff59c871cadd34765554fca58b8fea3510 /tools/coreutils | |
parent | 3ef655375a5edac9c4967394a213d10b631464a7 (diff) | |
download | upstream-b5193291bdde00e91c58e59029d5c68b0bc605db.tar.gz upstream-b5193291bdde00e91c58e59029d5c68b0bc605db.tar.bz2 upstream-b5193291bdde00e91c58e59029d5c68b0bc605db.zip |
ipq806x: onhub: Enable fstools_partname_fallback_scan
When fstools is unable to parse our root=<...> arg correctly, it can
fall back to scanning all block devices for a 'rootfs_data' partition.
This fallback was deemed wrong (or at least, a breaking/incompatible
change) for some targets, so we're forced to opt back into it with
fstools_partname_fallback_scan=1.
Without this, OnHub devices will use a rootfs-appended loop device for
rootfs_data instead of the intended 3rd partition.
While I'm at it, just move all the boot args into the 'cros-vboot'
build rule, instead of using the custom bootargs-append. All cros-vboot
subtargets here are using the same rootwait (to support both eMMC and
USB boot) and root/partition args.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
[ drop unrelated comments in commit description ]
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Diffstat (limited to 'tools/coreutils')
0 files changed, 0 insertions, 0 deletions