cy PCI driver - possible device id's

[Warner Losh]

On Tue, Jun 5, 2018, 4:57 PM Poul-Henning Kamp <phk at phk.freebsd.dk> wrote:

> --------
> In message <
> CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg at mail.gmail.com>,
> Conrad Meyer writes:
>
> >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.
>
> 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.
>

Devmatch can operate on an arbitrary loader.hints file. Just do a GENERIC
buildkernel, install it somewhere. Loader.hints gets created. Copy that
file to the target system and run devmatch...

Warner

-- 
> 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"
>