2007/9/19, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>: > > If you use ioport_map/unmap, then you really *should* access them with the > > proper iomem accessors (ioread/iowrite). The fact that it may happen to > > work (when using the default lib/iomap.c implementation, at least) on > > some architectures and with the current implementation still doesn't mean > > that you should necessarily use readb/writeb. > > Another reason we should enforce the use of ioread/iowrite is that some > platforms do daft things like map mmio type devices through indirect > register access. Sparc PCMCIA is a classic example. The only sane way to > make these work is to require ioread/iowrite is used with iomap > Hmm, we 've had bug reports about driver (madwifi-old-openhal) not working on Sparc64, can someone test if this is the case (the fact that we used readl/writel instead of ioread/iowrite on madwifi-old-openhal) ? It was really weird because we handle big-endian machines ok (madwifi-old-openhal on ppc worked fine). (ath5k was based on madwifi-old-openhal) -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
