From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 11 15:37:38 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA716106564A for ; Wed, 11 Jan 2012 15:37:38 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 4B6CE8FC13 for ; Wed, 11 Jan 2012 15:37:38 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Rl09R-00040K-3G for freebsd-hardware@freebsd.org; Wed, 11 Jan 2012 16:31:45 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Jan 2012 16:31:45 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Jan 2012 16:31:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Wed, 11 Jan 2012 16:31:29 +0100 Lines: 39 Message-ID: References: <4EDC0355.4030908@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120110 Thunderbird/9.0 In-Reply-To: Subject: Re: Hardware List X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2012 15:37:38 -0000 On 05/12/2011 10:19, 图潘 wrote: > I have looked at it, thank you, unfortunately it does not work as i had in > mind as I still have to identify the hardware itself, so I need to find out > the pci device id for each chipset (and/or vice versa). > > In hardware terms, I am working with device ids and not with chipsets. Is > there also a document covering the ids itself? No, and since drivers are constantly updated to supports new devices, the manuals often contain old and incomplete information. Unfortunately there is also no standard way in which drivers would present the list of all the devices they support, but it is often very easy to find that out from the code. Almost all drivers begin with a programmed list of their supported devices, looking similar to this in code: static struct { uint32_t id; uint8_t rev; const char *name; int quirks; } ahci_ids[] = { {0x43801002, 0x00, "ATI IXP600", 0}, {0x43901002, 0x00, "ATI IXP700", 0}, {0x43911002, 0x00, "ATI IXP700", 0}, {0x43921002, 0x00, "ATI IXP700", 0}, {0x43931002, 0x00, "ATI IXP700", 0}, {0x43941002, 0x00, "ATI IXP800", 0}, {0x43951002, 0x00, "ATI IXP800", 0}, {0x06121b21, 0x00, "ASMedia ASM1061", 0}, {0x26528086, 0x00, "Intel ICH6", AHCI_Q_NOFORCE}, {0x26538086, 0x00, "Intel ICH6M", AHCI_Q_NOFORCE}, {0x26818086, 0x00, "Intel ESB2", 0}, {0x26828086, 0x00, "Intel ESB2", 0}, {0x26838086, 0x00, "Intel ESB2", 0}, {0x27c18086, 0x00, "Intel ICH7", 0}, {0x27c38086, 0x00, "Intel ICH7", 0},