From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 10 Jul 2020 10:29:33 +0200 Subject: [PATCH 1/4] fs/squashfs: new filesystem In-Reply-To: <377389bc-a9ad-5271-ec1e-3df3c4053ca2@prevas.dk> References: <20200709175148.17193-1-joaomarcos.costa@bootlin.com> <20200709175148.17193-2-joaomarcos.costa@bootlin.com> <377389bc-a9ad-5271-ec1e-3df3c4053ca2@prevas.dk> Message-ID: <20200710102933.11a61099@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Rasmus, On Thu, 9 Jul 2020 21:50:03 +0200 Rasmus Villemoes wrote: > > +config SPL_FS_SQUASHFS > > + bool "Support SquashFS filesystems" > > + select FS_SQUASHFS > > Is there any reason U-Boot proper must support squashfs if the SPL does? > This isn't quite specific to this patch; I see a number of 'config > SPL_FOO' that either depends on or selects FOO (e.g. SPL_FS_FAT), and I > wonder why. Well, if your Linux kernel image and Device Tree are stored in a squashfs filesystem, then U-Boot proper needs SquashFS support, right ? And that is completely independent of whether the SPL has SquashFS support to be able to load U-Boot proper (which potentially could be stored on SquashFS as well). It's very much like the FAT filesystem case: if you have U-Boot proper and your Linux kernel image in a FAT filesystem, then the SPL needs FAT filesystem support to load U-Boot proper, and U-Boot proper needs FAT filesystem support to load the Linux kernel image. Am I missing something here ? Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com