From owner-freebsd-hardware@freebsd.org Tue May 23 16:34:33 2017 Return-Path: Delivered-To: freebsd-hardware@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CD2CD7B2BF for ; Tue, 23 May 2017 16:34:33 +0000 (UTC) (envelope-from paul@tmp.group) Received: from tmp.group (mail.tmp.group [IPv6:2a07:4580:b0d:27e::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C5AA915D4 for ; Tue, 23 May 2017 16:34:32 +0000 (UTC) (envelope-from paul@tmp.group) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tmp.group; s=210502017; h=Message-Id:Content-Type:Date:Subject:From:To:MIME-Version: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Uy+E+ivsHpR66+f0FMAQSZuG8HYATHQ9oCilCNd26sY=; b=icYRpMbAWUdIOk4xXqdr832l3R dgs2ARuMAJj8XWAOh0vKvAIlOkHIziCWx3JAzDFnj9Egg6aDhYuCSY3hYCXBXcIYCnTblLFZrMYzF HnXJYeIYibq6Sr9LJfdlf2UGn8je6oNME4QlnwYbq8kWLlR9unYhvmngEGoAlXSEoRF8=; MIME-Version: 1.0 To: "freebsd-hardware@freebsd.org" From: Subject: Dissecting information from pciconf Date: Tue, 23 May 2017 17:34:30 +0100 Importance: normal X-Priority: 3 Message-Id: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2017 16:34:33 -0000 Good day all, I do hope I chose the right list for this particular question, but I was ho= ping someone could fill me in on where pciconf derives the =E2=80=98hdr=3D= =E2=80=99 information it displays in =E2=80=98pciconf -l=E2=80=99; I am wor= king on a cross platform solution for mapping hardware support on various O= S, but I wish to start with FreeBSD. That being said the =E2=80=98key=E2=80=99 for hardware in my database must = logically be based off information retrieved from pciconf or lspci dependin= g which OS it is; so far the keyable fields I have found are. =E2=80=A2 CLASS,=C2=A00x0200000 0x[0200][0000] (This 0000 seems permenantly= unused) =E2=80=A2 CARD,=C2=A00x001e8086 0x[001e][8086] (SDevice SVendor) =E2=80=A2 CHIP,=C2=A00x100e80860 0x[100e][0860] (Device Vendor) =E2=80=A2 REV(ision)=C2=A00x02 0x[02] Ref, the revision =E2=80=A2 HDR(Header) 0x00 0x[00] Header ... that only appears to exist on = FreeBSD HDR is the tricky one, would I correct in believing, that if I had a cardbu= s Ethernet card and a pci version of the same type, every detail would be i= dentical EXCEPT the HDR? Or is it literally just an informatics value that can be ignored in generat= ion of a cross system hardware database?=20 Sent from Mail for Windows 10