Thread (9 messages) 9 messages, 4 authors, 2014-02-28

[PATCH v2 1/3] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases.

From: arnd@arndb.de (Arnd Bergmann)
Date: 2014-02-27 14:09:43
Also in: linux-devicetree, linux-pci, lkml

On Thursday 27 February 2014 13:09:57 Liviu Dudau wrote:
The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP
is wrong. It returns a mapped (i.e. virtual) address that can start from
zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most
architectures that use !CONFIG_GENERIC_MAP define.

Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help