On Thu, Oct 22, 2020 at 7:53 AM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > > On Tue, Sep 29, 2020 at 09:46:14PM +0100, Peter Robinson wrote: > > On Tue, Sep 29, 2020 at 9:41 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > > > On Tue, Sep 29, 2020 at 4:30 PM Ben Cotton <bcotton@xxxxxxxxxx> wrote: > > > > > > > > https://fedoraproject.org/wiki/Changes/CompressKernelFirmware > > > > > > > > == Summary == > > > > Compress Kernel Firmwares to reduce on disk size > > > > > > > > == Owner == > > > > * Name: [[User:pbrobinson| Peter Robinson]] > > > > * Email: [mailto:pbrobinson@xxxxxxxxxxxxxxxxx| pbrobinson@xxxxxxxxxxxxxxxxx] > > > > > > > > == Detailed Description == > > > > > > > > Since the linux 5.3 kernel there has been support for loading firmware > > > > from xz compressed firmware. The upstream linux-firmware respository > > > > is now over 900Mb, not including other kernel firmware that are in > > > > Fedora but come from other sources. By compessing the firmware with > > > > "xz -C crc32", the only option currently supported in the kernel, we > > > > can reduce the ondisk size of the firmware by almost half. > > > > > > > > > > I vaguely recall that there was some effort to add zstd support to > > > compress kernel stuff. Could we consider using that for this instead > > > of xz? Or is that still only for kernel modules? > > > > ATM the only thing that's upstream is xz hence why that's the only > > thing mentioned. > > zstd support has been merged for 5.9: > https://kernelnewbies.org/Linux_5.9#Support_for_ZSTD_compressed_kernel.2C_ramdisk_and_initramfs. > Does this support also extend to firmware? Nope, it's unrelated. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx