[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Use isenkram to get around the firmware problem?

On Sun, 2021-03-07 at 08:13 +0100, Petter Reinholdtsen wrote:
> The generic solution is to get the firmware-amd-graphics maintainer to
> add appstream metadata mapping to the PCI IDs supported by the package,
> <URL: http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html ;>
> and <URL: https://wiki.debian.org/AppStream/Guidelines ;>
> provide some clues on how to do this.

firmware-amd-graphics, like most (not all) firmware-* packages in non-
free, is generated from the firmware-nonfree source package.  I am one
of the maintainers but currently maks is doing most of the work on it.

Kernel modules do now mostly contain lists of associated firmware in
their metadata.  So in principle we could generate a list of device IDs
from a recent kernel build: for each packaged firmware file, find out
which module(s) refer to it, and add the device IDs the module(s)

However, we don't generally know which device IDs correspond to which
files.  So this would result in:

* Listing some device IDs that we don't have the firmware for
* Listing some device IDs that don't need firmware files (e.g. older
  Intel GPUs)

Is that kind of inaccuracy acceptable?


Ben Hutchings
friends: People who know you well, but like you anyway.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: