mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: PCI device search.
Date: Fri, 12 Oct 2001 17:04:11 +0200	[thread overview]
Message-ID: <20011012170411.A21169@come.alcove-fr> (raw)

Hi,

I have a device driver (drivers/char/sonypi in this case)
which can handle two cases:
	- on older hardware, it gets attached to a specific 
	  PCI device

	- on newer hardware, when the previous PCI device
	  is missing, it just uses a predefined set of
	  ioports to access the hardware. There is no PCI
	  device involved here.

I am wondering what is the cleanest way to program this. 
As I see it, I have two distinct choices:

	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).

Thanks,

Stelian.
-- 
Stelian Pop <stelian.pop@fr.alcove.com>
|---------------- Free Software Engineer -----------------|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|------------- Alcôve, liberating software ---------------|

             reply	other threads:[~2001-10-12 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 15:04 Stelian Pop [this message]
2001-10-12 20:55 ` Greg KH
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=20011012170411.A21169@come.alcove-fr \
    --to=stelian.pop@fr.alcove.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®