Re: Ideas for abstracting driver IO from bus implementation?

Alan Cox (alan@lxorguk.ukuu.org.uk)
Thu, 18 Mar 1999 13:14:18 +0000 (GMT)


> Am I right in thinking an I2O controller can:
> (a) be associated with a particular device (maybe on board physically).
> (b) be separate (say on the motherboard), and as such be capable of
> being assigned more than one device to look after (maybe at the
> whim of the O/S).

Or a combination of the two - for example a raid card that drives its own
NCR chips and any others it finds on the mainboard

> Am I right in thinking that attaching a PCI device to an I2O controller does
> not involve a renumbering of PCI devices and buses?

Correct.

> Does the real device still require/use I/O, IRQ, etc. resources when being
> driven from an I2O controller? I presume an I2O controller get resources
> through which it can be communicated with.

It uses motherboard resources. You can also reconfigure those motherboard
resources, but you have to beat the I2O controller around the head to do it.
I2O 2.0 is supposed to clean that up and handle I2O management of hot plug
PCI devices

> (3) A new type of resource token could be added representing interface types
> and access operations. The I2O driver could then interpose its own token
> in front or instead of the original one.

I was anticipating that you would need to have an "owner" for each device,
and that owner which now happens to always been the CPU might change. Then you'd
call the owners methods for reassignment notification.

Alan

-
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/