public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Greg KH <greg@kroah.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-pci@atrey.karlin.mff.cuni.cz, Greg KH <gregkh@suse.de>
Subject: Re: searching for pci busses
Date: Mon, 29 May 2006 17:59:39 -0400	[thread overview]
Message-ID: <447B6ECB.9080207@pobox.com> (raw)
In-Reply-To: <20060529214753.GD10875@kroah.com>

Greg KH wrote:
> On Sun, May 28, 2006 at 01:12:26AM +0159, Jiri Slaby wrote:
>> Hello,
>>
>> I want to ask, if there is any function to call (as we debated with Jeff), which
>> does something like this:
>> 1) I have some vendor/device ids in table
>> 2) I want to traverse raws of the table and compare to system devices, and if
>> found, stop and return pci_dev struct (or raw in the table).
> 
> What's wrong with pci_match_id()?
> 
> Or just using the pci_register_driver() function properly, which handles
> all of this logic for you?

These aren't PCI devices proper.  These are embedded non-PCI devices, 
which must search for an unrelated PCI device to figure out what type of 
platform they are on.

	Jeff




  reply	other threads:[~2006-05-29 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27 23:13 searching for pci busses Jiri Slaby
2006-05-29 21:47 ` Greg KH
2006-05-29 21:59   ` Jeff Garzik [this message]
2006-05-30 16:38     ` Greg KH
2006-05-30 16:52       ` Jon Smirl
2006-05-30 16:58         ` Greg KH
2006-05-30 17:00         ` Matthew Wilcox
2006-05-30 17:19           ` Jon Smirl
2006-05-30 17:02         ` Jiri Slaby

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=447B6ECB.9080207@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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