lkml.org 
[lkml]   [1999]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Ideas for abstracting driver IO from bus implementation?
Date
> I presume that you're making these values as tokens so that the I/O access
> routines (such as pcibios_write_config_byte) can be told how to access their
> devices.

No Im not.

> What exactly do you mean? Does I2O deal with whole buses rather than devices?
> Or is it a case of I2O allocating resources to a bus?

I2O owns entire devices on the bus. At startup you query each I2O I/O
processor and you get back things like

"I just drive my own on card I/O stuff"

"Im a motherboard controller, I know about your aic7xxx and your eepro100,
right now I'm configured to drive the eepro100 only"

You may find two controllers offering to handle the eepro100, or neither. You
may prefer to run the native driver. Who "owns" a PCI device is a run time
configurable item


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [from the cache]
©2003-2011 Jasper Spaans