From: Arjan van de Ven <arjan@infradead.org>
To: cckuo <chechun_kuo@sis.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: update pci device id
Date: Tue, 20 Jun 2006 16:06:42 +0200 [thread overview]
Message-ID: <1150812402.2891.202.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <OF39A58CF4.C4A06C9A-ON48257193.004A1ACB@sis.com.tw>
On Tue, 2006-06-20 at 21:28 +0800, cckuo wrote:
> Dear All:
> Recently my company, sis, releases some new platforms for intel socket 775,
> and AMD socket 939. I have read the MAINTAINERS and cannot find someone whom
> I can let him help me to add the pci device id.
> If someone knows who takes charge of this part, please let me know.
Hi,
the answer is a bit complex; I'll try to break it down in steps ...
step 1) the text database as used by lspci
This is quite easy, just go to http://pciids.sourceforge.net/ and add
your pci ids to the database
step 2) the drivers
this is a bit more work, basically this is about teaching individual
drivers that support your hardware about your new IDs.
for example the i810-like audio driver has a table like this:
static struct pci_device_id snd_intel8x0_ids[] __devinitdata = {
{ 0x8086, 0x2415, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DEVICE_INTEL }, /* 82801AA */
{ 0x8086, 0x2425, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DEVICE_INTEL }, /* 82901AB */
{ 0x8086, 0x2445, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DEVICE_INTEL }, /* 82801BA */
{ 0x8086, 0x2485, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DEVICE_INTEL }, /* ICH3 */
if your hw is compatible, just add your ID, test the new river (since
you have the hardware) and send a patch to the driver mainter and/or the
lkml mailing list
Does this answer your question?
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2006-06-20 14:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.VT2rwoX1M/2O/aO5crhlRDNx4YA@ifi.uio.no>
[not found] ` <fa.Zp589GPrIISmAAheRowfRgZ1jgs@ifi.uio.no>
2006-06-20 5:35 ` [patch] increase spinlock-debug looping timeouts (write_lock and NMI) Dave Olson
2006-06-20 6:39 ` Andrew Morton
2006-06-20 6:53 ` Dave Jones
2006-06-20 7:37 ` Nick Piggin
2006-06-20 8:03 ` Andrew Morton
2006-06-20 8:33 ` Ingo Molnar
2006-06-20 9:37 ` Nick Piggin
2006-06-20 9:51 ` Ingo Molnar
2006-06-20 10:59 ` Nick Piggin
2006-06-20 13:04 ` Arjan van de Ven
2006-06-20 13:28 ` update pci device id cckuo
2006-06-20 14:06 ` Arjan van de Ven [this message]
2006-06-20 13:36 ` [patch] increase spinlock-debug looping timeouts (write_lock and NMI) Nick Piggin
2006-06-20 14:53 ` Arjan van de Ven
2006-06-20 15:16 ` Nick Piggin
2006-06-20 16:27 ` Nick Piggin
2006-06-20 8:43 ` Arjan van de Ven
2006-06-20 16:11 ` Dave Olson
2006-06-20 21:10 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1150812402.2891.202.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=chechun_kuo@sis.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®