Re: Bug#1055206: ITP: asahi-fwextract -- Asahi Linux firmware extractor
Hello,
Filling out some of the missed information below and also providing some
random thoughts of my own on this.
On Thu, Nov 02, 2023 at 09:49:51AM +0100, Tobias Heider wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Tobias Heider <me@tobhe.de>
> X-Debbugs-Cc: debian-devel@lists.debian.org
>
> * Package name : asahi-fwextract
> Version : 0.6.12
> Upstream Authors:
^^^^ Asahi Linux Contributors
> URL :
^^^^ https://github.com/AsahiLinux/asahi-installer/tree/main/asahi_firmware
> * License : MIT
> Description : Asahi Linux firmware extractor
>
> Scripts to extract firmware blobs from an EFI partition set up by the
> Asahi Linux installer.
>
> I am planning to maintain this as part of the bananas team.
>
The firmware extractor is part of upstreams (custom) installer-repository.
It also depends on asahi-scripts[1] which contains the asahi-fwupdate
utility, et.al. This also contains initramfs integration to make the
firmwares available during early boot and then provided as a tmpfs
under /lib/firmware/vendor in the running system.
Preliminary packaging is available at:
https://salsa.debian.org/bananas-team/asahi-fwextract
https://salsa.debian.org/bananas-team/asahi-scripts
Some random thoughts:
AIUI currently only initramfs-tools integration is shipped, but
maybe it would be good to also provide dracut integration (as provided
by upstream, if possible to integrate with debians dracut packaging)?!
I don't see any asahi-scripts ITP yet. Since asahi-scripts is a
dependency of asahi-fwextract I would have expected one to be posted
before this. Maybe the multiple-upstream-tarballs feature could be used
to package them together? But it's possibly more problems then benefits.
Maybe the asahi-scripts should have a less generic binary package name? and
split into multiple packages?
Regards,
Andreas Henriksson
[1]: https://github.com/AsahiLinux/asahi-scripts
Reply to: