Date: Tue, 05 Jun 2018 20:49:46 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: cem@freebsd.org Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: cy PCI driver - possible device id's Message-ID: <33255.1528231786@critter.freebsd.dk> In-Reply-To: <CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail.com> References: <CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439%2Bj34rvLaqo2PMv2VQ@mail.gmail.com> <32229.1528222775@critter.freebsd.dk> <CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--------
In message <CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail=
.com>, Conrad Meyer writes:
>We already have exactly this =3DE2=3D80=3D94 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.
Yes, and that's good and great, but it only works if you have
the modules installed on the machine to examine.
For scenarios like NanoBSD it would be nice if devmatch had a
built-in "fall-back" table (created at compile time) to suggest
modules not present in the local filesystem.
-- =
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 incompetence=
.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33255.1528231786>