Messages in this thread | | | Subject | Re: port_t again, sorry didn't type the whole thing. | From | Jes Degn Soerensen <> | Date | 02 Jun 1998 15:45:07 +0200 |
| |
>>>>> "Janos" == Janos Farkas <Janos.Farkas-nouce/priv-#DyQtpWAZZ3xFtWelno54PCx.kde@lk9qw.mail.eon.ml.org> writes:
Janos> The I/O port number range, thus the C type needed to represent Janos> it is not just a function of the CPU architecture, but more so Janos> of the bus type (think PCI). Also (IMHO), the in/out Janos> routines/macros are not quite useful for multiple (I/O) buses Janos> reachable through bridges. Although handling these "extra" Janos> situations seems to be uninteresting for almost everyone but Janos> me.. :)
Not just for you I'd say ;-)
Adding a bus identifier parameter to the inb/outb macros would be nice for people having multiple different busses which are not merged into the same IO space as it is done on the PC.
Jes
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |