Device Drivers For Different IO Bus architectures



Hello Folks
I am trying to find out some details about writing device drivers .
If a device is capable of talking to different IO buses like PCI /
ISA / PCI express etc .
Is writing a driver to it on a unix / linux system be different If so
in what way .

To elaborate the question more let us say a particular device could
have different firmware on so it can talk to to CPU over different IO
Bus as required and if the interface to the layer2 / firm ware is kept
as same as possible , would the driver writing be any different .

Basically i am trying to find out if writing device drivers is
different based on the IO bus used.
I believe it should not be so , but i would like to here from the
experts there .

thanks
subra

.



Relevant Pages

  • Re: Device Drivers For Different IO Bus architectures
    ... I am trying to find out some details about writing device drivers. ... ISA / PCI express etc. ... I think it can't be feasible to unify different I/O buses interfaces on ...
    (comp.arch.embedded)
  • Re: howto determine network device unit number? device.hints?
    ... Could it be how your BIOS and hardware set up the PCI IDSEL lines at boot? ... Based on the data you've provided about the issue to date, my best guess is that something in the above is different on your system (which is why I mentioned IDSEL lines -- the mechanism PCI uses to actually assign bus numbers electrically). ... Normally the behaviour of FreeBSD's bus probes is well known -- nexus is walked for child buses, then these buses are plumbed into NEWBUS, e.g. cpu0...cpuN on nexus itself, PCI buses, and PCI subordinate buses in that order. ...
    (freebsd-net)
  • Re: howto determine network device unit number? device.hints?
    ... Could it be how your BIOS and hardware set up the PCI IDSEL lines at boot? ... Based on the data you've provided about the issue to date, my best guess is that something in the above is different on your system (which is why I mentioned IDSEL lines -- the mechanism PCI uses to actually assign bus numbers electrically). ... Normally the behaviour of FreeBSD's bus probes is well known -- nexus is walked for child buses, then these buses are plumbed into NEWBUS, e.g. cpu0...cpuN on nexus itself, PCI buses, and PCI subordinate buses in that order. ...
    (freebsd-questions)
  • Re: PQOAL PCI BusID vs Bus Number Problem
    ... Original intention is add support for system with multiple PCI buses ... with bus number. ... In most cases, the BusID parameter would be zero, ...
    (microsoft.public.windowsce.platbuilder)