Date: Tue, 5 Jun 2018 13:34:22 -0700 From: Conrad Meyer <cem@freebsd.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: cy PCI driver - possible device id's Message-ID: <CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail.com> In-Reply-To: <32229.1528222775@critter.freebsd.dk> References: <CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439%2Bj34rvLaqo2PMv2VQ@mail.gmail.com> <32229.1528222775@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
We already have exactly this =E2=80=94 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@phk.freebsd.dk> wro=
te:
> --------
> In message <CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439+j34rvLaqo2PMv2VQ@mail.gmai=
l.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@FreeBSD.ORG | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetenc=
e.
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org=
"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg>