linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Grant Coady <gcoady.lk@gmail.com>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Brent Casavant <bcasavan@sgi.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	akpm@osdl.org, jeremy@sgi.com
Subject: Re: [PATCH] Move various PCI IDs to header file
Date: Mon, 08 May 2006 10:35:48 +0200	[thread overview]
Message-ID: <445F02E4.5000004@sgi.com> (raw)
In-Reply-To: <1147077120.2888.5.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:
> On Mon, 2006-05-08 at 09:55 +0200, Jes Sorensen wrote:
>> So much for being able to go through the pci_ids.h file to get an idea
>> about whether or not a device may have a chance of being supported :(
> 
> that wasn't there ever anyway..
> 
> modules.pcimap is more like it anyway

Wasn't bullet proof since some people just stuck it in their drivers due
to laziness, but it was a pretty good indicator. I've gone through it
many times to see if I could find a match for a device ;(

Anyway ....

Cheers,
Jes

  reply	other threads:[~2006-05-08  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 23:09 [PATCH] Move various PCI IDs to header file Brent Casavant
2006-05-05  0:37 ` Randy.Dunlap
2006-05-05  5:45   ` Jes Sorensen
2006-05-05 13:34     ` Greg KH
2006-05-13  4:29       ` Jeff Garzik
2006-05-05 16:27     ` Randy.Dunlap
2006-05-05 22:37       ` Grant Coady
2006-05-08  7:55         ` Jes Sorensen
2006-05-08  8:31           ` Arjan van de Ven
2006-05-08  8:35             ` Jes Sorensen [this message]
2006-05-05 14:09 ` Jes Sorensen

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=445F02E4.5000004@sgi.com \
    --to=jes@sgi.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=bcasavan@sgi.com \
    --cc=gcoady.lk@gmail.com \
    --cc=jeremy@sgi.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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;
as well as URLs for NNTP newsgroup(s).