At least as it is used right now, the ioport and iomem resources might
as well be considered to be a "CPU bus", in the sense that they are
organized around how a ia32 CPU sees the bus.
So in that sense it certainly would apply to MCA too.
However, this is something that might change later. IF we decide that
we really want to make the resources be more oriented towards the bus
addressing (which implies that we'd change "inb/outb/readb/writeb" too:
this is a MAJOR change, and not likely to happen in the next few years),
at that point MCA might either not be an issue any more or we'd give it
a resource of its own..
So the answer is "at least for now, possibly forever".
Linus
-
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/