All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: John Ernberg <john.ernberg@actia.se>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
	Jonas Blixt <jonas.blixt@actia.se>
Subject: Re: [Buildroot] [PATCH] fs/squashfs: Allow to disable compression of the filesystem
Date: Mon, 30 Dec 2024 22:42:51 +0100	[thread overview]
Message-ID: <20241230224251.73600ba3@windsurf> (raw)
In-Reply-To: <20241227103623.1608053-1-john.ernberg@actia.se>

On Fri, 27 Dec 2024 10:36:35 +0000
John Ernberg <john.ernberg@actia.se> wrote:

> Devices with large amounts of flash but operating in connectivity-
> constrained areas can benefit from using uncompressed images as this
> allows delta updates using binary diff algorithms.
> 
> Connectivity-constrained areas in this context are defined as areas
> where the connection is very slow, unstable, etcetera, where it is
> difficult to transfer data in large scale.
> 
> Add a "none" option to the compression menu and map it to the mksquashfs
> -no-compression flag to enable this feature.
> Disable the ability to select extreme compression in this case as that
> makes absolutely no sense combined with no compression.
> 
> Signed-off-by: John Ernberg <john.ernberg@actia.se>
> ---
>  fs/squashfs/Config.in   | 6 ++++++
>  fs/squashfs/squashfs.mk | 2 ++
>  2 files changed, 8 insertions(+)

Thanks a lot for this patch, makes sense, so I've applied to our master
branch!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-12-30 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 10:36 [Buildroot] [PATCH] fs/squashfs: Allow to disable compression of the filesystem John Ernberg
2024-12-30 21:42 ` Thomas Petazzoni via buildroot [this message]

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=20241230224251.73600ba3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=john.ernberg@actia.se \
    --cc=jonas.blixt@actia.se \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.