On Thu, Sep 8, 2011 at 10:33 AM, Randy Dunlap <rdunlap@xxxxxxxxxxxx> wrote: > On 09/01/11 19:50, Amos Kong wrote: >> From: Amos Kong <kongjianjun@xxxxxxxxx> >> >> The right filename should be Documentation/io-mapping.txt > > Once upon a time we had both IO-mapping.txt and io-mapping.txt. > To fix that "problem," IO-mapping.txt was renamed to > "bus-virt-phys-mapping.txt". I think that this reference should > be changed to "bus-virt-phys-mapping.txt" instead of to io-mapping.txt. Documentation/io-mapping.txt is about "mapping small regions of an I/O device to the CPU," which *sounds* like it would be what you want for device registers, but from what I can tell, it's really about making large WC (write-coalescing) mappings for framebuffers. That's not what you want for normal device registers because you don't want WC. Documentation/bus-virt-phys-mapping.txt does contain a tiny reference to the ioremap() you want in this case and would be more useful than io-mapping.txt. But I think the best reference is to Documentation/DocBook/deviceiobook.tmpl, which is all about accessing device registers. >> -See Documentation/IO-mapping.txt for how to access device registers >> +See Documentation/io-mapping.txt for how to access device registers >> or device memory. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
