All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stelian Pop <stelian.pop@fr.alcove.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI device search.
Date: Fri, 12 Oct 2001 13:55:56 -0700	[thread overview]
Message-ID: <20011012135556.A21296@kroah.com> (raw)
In-Reply-To: <20011012170411.A21169@come.alcove-fr>
In-Reply-To: <20011012170411.A21169@come.alcove-fr>

On Fri, Oct 12, 2001 at 05:04:11PM +0200, Stelian Pop wrote:
> 
> 	1. Create a PCI driver (pci_device_id, struct pci_driver etc)
> 	and in init_module call pci_module_init. If it fails,
> 	assume the driver deals with newer hardware and 
> 	call 'by hand' the 'probe' routine from pci_driver struct.
> 
> 	2. Not use the PCI driver infrastructure, and in
> 	init_module just call pci_find_device manually searching
> 	for older hardware, if it is present go further, if
> 	it fails assume newer hardware and go further.
> 
> What is considered to be the best way to do it ?
> (this is _not_ a hotplug device if it matters).

I'd say 1.  If a device is hotpluggable or not does not matter.  For
2.5, the boot process will be able to load modules for all PCI
devices seen in the system.  In order for that to happen, they need to
use the MODULE_DEVICE structure and the 2.4 pci driver subsystem.

(which it looks like almost none of the current SCSI driver do...)

thanks,

greg k-h

  reply	other threads:[~2001-10-12 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 15:04 PCI device search Stelian Pop
2001-10-12 20:55 ` Greg KH [this message]
2001-10-12 21:15   ` Jeff Garzik
2001-10-13 12:51     ` Stelian Pop
2001-10-13 20:19       ` Jeff Garzik

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=20011012135556.A21296@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.