From owner-freebsd-hackers@freebsd.org  Tue Jun  5 20:49:54 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A91F7FF5F58
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Tue,  5 Jun 2018 20:49:54 +0000 (UTC)
 (envelope-from phk@critter.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 44C5B7166B;
 Tue,  5 Jun 2018 20:49:54 +0000 (UTC)
 (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 by phk.freebsd.dk (Postfix) with ESMTP id E73681484E;
 Tue,  5 Jun 2018 20:49:47 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w55KnkEf033257
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 5 Jun 2018 20:49:46 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost)
 by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w55KnkNg033256;
 Tue, 5 Jun 2018 20:49:46 GMT (envelope-from phk)
To: cem@freebsd.org
cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Subject: Re: cy PCI driver - possible device id's
In-reply-to: <CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <CAHC0YgfPmPmOQVmHD_uY8d7qHbHLrc439+j34rvLaqo2PMv2VQ@mail.gmail.com>
 <32229.1528222775@critter.freebsd.dk>
 <CAG6CVpXKGrN_Ee2tBwyLDNgLL9CFYPhsjn9QLbOBT_zaf55esg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <33254.1528231786.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 05 Jun 2018 20:49:46 +0000
Message-ID: <33255.1528231786@critter.freebsd.dk>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2018 20:49:54 -0000

--------
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=
.