From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] fs/squashfs: new filesystem
Date: Wed, 15 Jul 2020 17:56:11 -0400 [thread overview]
Message-ID: <20200715215611.GZ6227@bill-the-cat> (raw)
In-Reply-To: <20200710111350.4ef91b67@windsurf>
On Fri, Jul 10, 2020 at 11:13:50AM +0200, Thomas Petazzoni wrote:
> On Fri, 10 Jul 2020 10:54:24 +0200
> Rasmus Villemoes <rasmus.villemoes@prevas.dk> wrote:
>
> > > It's very much like the FAT filesystem case: if you have U-Boot proper
> > > and your Linux kernel image in a FAT filesystem,
> >
> > No, this is very much _not_ like the above. In this paragraph, you
> > combine "U-Boot proper and your Linux kernel", imposing an implicit
> > assumption that they are stored in the same way. Sure, _if_ both these
> > items are stored in squashfs images (possibly the same, possibly
> > distinct), then the thing that loads the respective images obviously
> > needs squashfs (or FAT, or whatnot) support.
> >
> > My point is that it's possible that, say, U-Boot proper is stored in a
> > FAT file system, and the kernel is stored in a UBI volume. So SPL needs
> > FAT support. Why should I be forced to compile FAT support into U-Boot
> > proper if U-Boot proper never needs to access a FAT filesystem? And the
> > same for squashfs. Or any of the drivers or DM_ frameworks that do that
> > "depends on" or "select".
>
> Ah, I absolutely agree that it should be possible to have Squashfs in
> both SPL and U-Boot proper, or only in SPL or only in U-Boot proper.
>
> It was not clear in your initial e-mail that this was the issue you
> were pointing.
Note that on this point the question is, do we have a use case for
falcon mode and loading linux from squashfs? I assume the answer is
yes, and that's why we would want to have squashfs be enabled in SPL.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200715/cac9a7a6/attachment.sig>
next prev parent reply other threads:[~2020-07-15 21:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 17:51 [PATCH 0/4] Add support for the SquashFS filesystem Joao Marcos Costa
2020-07-09 17:51 ` [PATCH 1/4] fs/squashfs: new filesystem Joao Marcos Costa
2020-07-09 19:50 ` Rasmus Villemoes
2020-07-09 20:19 ` Joao Marcos Costa
2020-07-10 8:29 ` Thomas Petazzoni
2020-07-10 8:54 ` Rasmus Villemoes
2020-07-10 9:13 ` Thomas Petazzoni
2020-07-15 21:56 ` Tom Rini [this message]
2020-07-15 21:55 ` Tom Rini
2020-07-09 17:51 ` [PATCH 2/4] fs/squashfs: add filesystem commands Joao Marcos Costa
2020-07-09 17:51 ` [PATCH 3/4] fs/squashfs: add sources for zlib decompression Joao Marcos Costa
2020-07-15 19:37 ` Thomas Petazzoni
2020-07-09 17:51 ` [PATCH 4/4] fs/squashfs: add support " Joao Marcos Costa
2020-07-15 20:11 ` [PATCH 0/3] squashfs fixes Thomas Petazzoni
2020-07-15 20:11 ` [PATCH 1/3] cmd/sqfs.c, include/fs.h: fix build failures, don't expose do_sqfs_*() functions globally Thomas Petazzoni
2020-07-15 20:11 ` [PATCH 2/3] fs/squashfs: use "struct disk_partition" instead of "disk_partition_t" Thomas Petazzoni
2020-07-15 20:11 ` [PATCH 3/3] fs/squashfs: do not use CMD_RET_* defines in the filesystem code Thomas Petazzoni
2020-07-16 7:51 ` [PATCH 0/3] squashfs fixes Joao Marcos Costa
2020-07-16 8:33 ` Thomas Petazzoni
2020-07-15 20:22 ` [PATCH] fs/squashfs/sqfs.c: use sqfs_read_sblk() in sqfs_probe() Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200715215611.GZ6227@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox