Ok we were talking cross purposes. I thought you wanted ioremap to set the
big/little endian and policy on write combining.
> I want a PCI_ioremap so that I can pass in data that is _clearly_ PCI
> related -- the pci_dev. I also want an ISA_ioremap because it would be
> stupid to pretend crufty old drivers could gen up a fake pci_dev struct
> just so it could pass off the info to the new pci_ioremap. All the
> important bits in the pci_dev were filled in by arch specific code
> at boot time. (I am fortunate that while I have multiple PCI busses, I
> only ever have one EISA bus, so I never have to hunt down the proper I/O
> space for that case.)
This makes complete and total sense
-
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/