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

Re: Use isenkram to get around the firmware problem?



On Fri, 2021-04-23 at 23:14 +0200, Cyril Brulebois wrote:
> Hi Ben,
> 
> And sorry for the long delay before replying to your offer.
> 
> Ben Hutchings <ben@decadent.org.uk> (2021-03-12):
> > 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)
> > support.
> > 
> > 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?
> 
> That would look way better than the status quo, and I'd be happy to get
> that kind of information, thanks!

Here's what I came up with:
https://salsa.debian.org/kernel-team/firmware-nonfree/-/merge_requests/19

The generated files can be seen in:
https://people.debian.org/~benh/firmware-metainfo/

Ben.

-- 
Ben Hutchings
I'm not a reverse psychological virus.
Please don't copy me into your signature.

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


Reply to: