Re: Ideas for abstracting driver IO from bus implementation?

David Howells (David.Howells@nexor.co.uk)
Thu, 18 Mar 1999 15:53:13 GMT

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Mike Eisler: "Re: DES module in kernel?"
Previous message: Giuliano Procida: "RE: Token Ring layer clobbers first byte of saddr"
In reply to: jpranevich@lycos.com: "APM not resetting keyboard properly?"

> The I2O controller shares some busses with the CPU but not all. When it
> reports what it has you get a report that seperates devices only it can see
> from those you (the cpu) can directly see
>...
> > Does the I2O controller actually change the settings on the card itself, or
> > does the O/S have to do that?
>
> The OS does it.

I take it that this is not true of buses that the CPU can't see, and that the
I2O controller looks after those.

Actually, I guess this is mostly irrelevent because the CPU won't share
IRQ/ioport/etc space with the I2O controller on these buses.

Wrt to my configuration manager's bus abstraction, a bus is dealt with by it's
bridge device.

> The CPU->I2O controller interface is defined right now for PCI. The I2O
> controller can itself control anything the hardware allows it to on the
> busses. Indeed I2O would work over ISA 8) it would just suck a lot that way.

I'm not sure, but I think you may have misunderstood what I meant... Can the
I2O controller configure and control ISA devices, such as a PnP SCSI card.

David Howells

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

Next message: Mike Eisler: "Re: DES module in kernel?"
Previous message: Giuliano Procida: "RE: Token Ring layer clobbers first byte of saddr"
In reply to: jpranevich@lycos.com: "APM not resetting keyboard properly?"