On 08/20/2015 10:04 AM, Hans de Goede wrote:
ubifs does not go though the generic block layer because mtd devices are special, so the "any" filesystem option to sysboot does not work, this adds support for a "ubifs" filesystem to the sysboot command which makes it possible to boot from ubifs using an extlinux.conf file.
Why are they special? Surely ubifs support can be integrated into the filesystem layer, thus removing the need for patches 1 and 3 in this series?
The problem here is that in patch 3,BOOTENV_DEV_UBIFS and BOOTENV_SHARED_UBIFS duplicate the file looping logic that already exist in other block device scanning macros. Naively it looks like it should be possible to avoid that completely. One change I vaguely had in mind for the distro boot scripts was to add a user-configurable environment variable to specify which of extlinux, script (and later perhaps Android, ...) support each partition was scanned for. Any time a change like that is made, with this patch applied first, that change would have to be replicated twice (and potentially n times if we continue down this path).
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
