Bug#1079188: nvidia-legacy-340xx-kernel-dkms: Add Appstream metainfo announcing HW support

[Andreas Beckmann]

On 1/25/25 12:59, Petter Reinholdtsen wrote:

>> ++    <modalias>pci:v000010DEd000006FDsv*</modalias>
>>
>> isn't that a wildcard matching all nvidia gpus?
> 
> According to /usr/share/misc/pci.ids it is this entry:
> 
>    10de  NVIDIA Corporation
>      06fd  G98 [Quadro NVS 295]
> 
>> Shouldn't that be restricted to the ones supported by this driver?
> 
> Yes.  And if you know more hardware supported by the driver, it should
> be listed too. :)

For the EoL 340 series, this is debian/end-of-life.ids
These are the ones supported by 340xx but not later series. The full 
list would be debian/nv-readme.ids

The naming of the eol list file is not consistent between the series 
(since it is not part of any automated processing), but we could change 
that ...

>> For patch simplification, don't create the new file with a patch but
>> place it in debian/.
> 
> As I believe in general the AppStream metadata XML files should be
> shared across Linux distributions and provided from upstream, I tend to
> create a upstreamable patch for the change.

I don't think that applies here, especially not for the EoL driver series.
At some point Nvidia introduced a .json file containing PCI ID and 
supported driver information, but I don't parse that, yet. Instead I 
still get the IDs from the README...

As we should have most (all?) of the metadata needed for the xml file in 
the package, I'd prefer to generate that on the fly during package build 
instead of carrying around a potentially outdated copy.


Anway, I think we should start implementing that for the main line 
driver (src:nvidia-graphics-drivers) first and then see what needs to 
change for the relevant legacy or tesla series

Andreas