Date: Tue, 23 May 2017 17:34:30 +0100 From: <paul@tmp.group> To: "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org> Subject: Dissecting information from pciconf Message-ID: <E1dDClQ-0004lX-CI@tmp.group>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1dDClQ-0004lX-CI>