Benjamin> And what about simply having a struct io_bus containing
Benjamin> function pointers to read/write and ioremap routines ? This
Benjamin> way, we could hide all the i/o range offset issues when
Benjamin> using several busses (we do have such problems with the ppc,
Benjamin> especially with IDE, see recent discussion of linuxppc-dev
Benjamin> mailing list). Each driver would have an bus structure
Benjamin> associated with the device, eventually provided by the
Benjamin> resource tree, and the only overhead of i/os could be the
Benjamin> indirect function call.
This could certainly be done, it would be very `pretty' and very very
inefficient. It would basically end up looking like something like UDI
(*shiver*).
Jes
-
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/