[PATCH 3/3] staging: tidspbridge: remove memory consistency from TODO list
felipe.contreras at gmail.com
Mon Oct 11 07:16:54 EDT 2010
On Mon, Oct 11, 2010 at 1:40 PM, Arnd Bergmann <arnd at arndb.de> wrote:
> On Sunday 10 October 2010, Felipe Contreras wrote:
>> The mempool area is not handled by the kernel any more.
> But tidspbridge still uses ioremap to set up the mapping for RAM,
> even though it now is outside of the kernel linar mapping.
Which is what ioremap() complained about, and how Russell King
suggested to solve the issue.
> You should really only use ioremap on MMIO registers, nothing
> else. These registers are marked as __iomem pointers and can only
> be passed into functions that talk to the hardware like iowrite32
> or writel, but not used like memory.
More information about the linux-arm-kernel