cy PCI driver - possible device id's

[Conrad Meyer]

We already have exactly this — a precise convention
("MODULE_PNP_INFO") and tool ("kldxref" for extracting the data, and
"devmatch" for suggesting matches), initiated by Warner.  This work
has been ongoing, in stops and starts, for years.  Lakhan is
converting non-compliant drivers to the convention.

Conrad

On Tue, Jun 5, 2018 at 11:19 AM, Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:
> --------
> In message <CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439+j34rvLaqo2PMv2VQ at mail.gmail.com>, Lakhan Shiva writes:
>
>>I am working on converting PCI drivers attachments to be table driven.
>
> Can we please invent some kind of "typographic" convention which
> allows these tables to be extracted from the kernel source code,
> so that we can have an utility which suggests which drivers to
> load, by consulting such an extracted table ?
>
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"