From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 5 03:30:39 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B150106564A; Tue, 5 Apr 2011 03:30:39 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 395AE8FC16; Tue, 5 Apr 2011 03:30:39 +0000 (UTC) Received: by pxi6 with SMTP id 6so4915680pxi.17 for ; Mon, 04 Apr 2011 20:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hhUgOKOTTX5IVeJ/iJVY0vN/PGVOLViWK+I3Pe19mng=; b=UZWbGP8GPKhC5RrZEyNsT96D3ddAsnY0mri4D/jUKj5qm+KfAPhVyPI3NNgILKTK4k veRdYoWDZzBPU5wVBpbxEGyaXEK7k/r2f8YF63OLfams9MuYhopwD2v3XYZAD1/5O3Sf 2fk+8RuN/QK1qSp2fkuAvsas7EoDKL+pm9RTo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jfi1gXOFN34WPJvMReqB6MgjJaAXb6Pd4bItoQiArpz6jUcBsiA+3g/89SdnnO+nWG pWQuQFuAvP36vwAnXbuxQdczmvc4rqVFCXCwgBLD0fo8bxaGbkxBQdaDRh8gpnmq2TM0 8BlL0k3Ab6qc3Was3gZMjRaUzij+fbiveSSVc= MIME-Version: 1.0 Received: by 10.142.248.21 with SMTP id v21mr7079769wfh.56.1301974238700; Mon, 04 Apr 2011 20:30:38 -0700 (PDT) Received: by 10.68.42.3 with HTTP; Mon, 4 Apr 2011 20:30:38 -0700 (PDT) In-Reply-To: <4D9A0836.7070403@FreeBSD.org> References: <20110404141016.GL71940@rincewind.paeps.cx> <4D9A0836.7070403@FreeBSD.org> Date: Mon, 4 Apr 2011 20:30:38 -0700 Message-ID: From: Garrett Cooper To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: hackers@freebsd.org Subject: Re: Updating PCI vendors database X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2011 03:30:39 -0000 On Mon, Apr 4, 2011 at 11:04 AM, Doug Barton wrote: > On 04/04/2011 07:10, Philip Paeps wrote: >> >> It looks like our /usr/share/misc/pci_vendors list (used only by pciconf >> as >> far as I can tell) has become rather stale. =A0We also appear to be trac= king >> sources which no longer exist. >> >> Would anyone object if I updated this list to source the same database >> used by >> Linux distributions at http://pciids.sourceforge.net/v2.2/pci.ids? >> >> It helps that our pciconf looks to be compatible with that format. =A0We >> just >> ignore subvendor and subdevice, but it doesn't appear to matter that the >> file >> contains this information. >> >> I could cull the subvendor/subdevice from the list though. >> >> Any views? > > Having read this thread, and the last one, my opinion is, let's do it > already. :) =A0Repo churn should not, under any circumstances, be a > consideration in technical improvements. I agree with those who have said > that the new list should be confirmed to be a superset of the old, and > anything missing should be merged in. Checking with Jack about Intel stuf= f > is also reasonable, as would be cross-checking with what NetBSD and OpenB= SD > are doing (and perhaps communicating with them about your work). 1. People may have automation that depends on this output. 2. Some braindead SCMs may be problematic with this change (p4? *COUGH*). Someone at $WORK recently backported a copy of pci_vendors from CURRENT to STABLE without any issues (needed a few PCI IDs for new hardware), but that might not have been as true with this shift to using pci.ids. > So, not a slam-dunk, but definitely a clear path forward. Oh, and I > personally don't see a problem with MFC'ing this, but I'm willing to be > convinced. Thanks, -Garrett