Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add modalias support #59

Open
julian-klode opened this issue Mar 7, 2018 · 5 comments
Open

Add modalias support #59

julian-klode opened this issue Mar 7, 2018 · 5 comments
Labels
feature:device Related to device and firmware metadata

Comments

@julian-klode
Copy link

In order to migrate the driver finding in Ubuntu to PackageKit, we think it makes sense to use AppStream to do that. I think what we have to do for that is

  1. Document the modalias list for provides for the appstream yaml format
  2. extract modalias list from the packages Modaliases field, which looks like this:
    Modaliases: nvidia(pci:v000010DEd000005E7sv*sd00000595bc03sc*i*, ...)
  3. Make software-properties query appstream for modaliases.

Does that sound about right?

@julian-klode
Copy link
Author

We don't have to do that to get the task of porting software-properties done, but it certainly would be nice :)

@ximion
Copy link
Owner

ximion commented Mar 7, 2018

Everything is already there in appstream-generator to support this. The respective packages just need a metainfo file specifying modaliases.
See https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-provides (modalias YAML field exists as well) as well as this Debian Wiki entry: https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware

You can also query for components that support a given modalias using appstreamcli what-provides modalias '<modalias_string>'
So, as far as I know, the only thing needed is more metainfo files.

@iainlane
Copy link
Collaborator

iainlane commented Mar 7, 2018 via email

@ximion
Copy link
Owner

ximion commented Mar 7, 2018

Can we generate this from the apt metadata instead of / as well as making pkgs provide the metainfo file?

I guess so (don't we do a similar hack for GStreamer plugins?), although I would of course very much prefer any such solution to be just a stopgap to proper metainfo files.
I actually wonder whether writing a script that generates the metainfo files once from apt data makes more sense (and then add those files to the packages proper). Other distros may be very interested in adopting the metainfo files as well, in that case.

@ximion ximion added the feature:device Related to device and firmware metadata label Aug 22, 2018
@Conan-Kudo
Copy link
Contributor

Conan-Kudo commented Aug 5, 2019

@ximion Historically, in RPM distributions, the mod-aliases have been part of rpm Provides and Supplements tags for kernel modules subpackaged out in the kernel package and kmod packages.

I'm not sure whether we've added too many of these other than for the NVIDIA driver to metainfo...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature:device Related to device and firmware metadata
Projects
None yet
Development

No branches or pull requests

4 participants