The specific cases I have in mind are frame buffer and MMIO regions used by
frame buffer devices. Furthermore this would allow us to get rid of the ugly
zorro_{config,unconfig}_board() calls in the drivers for Zorro bus devices.
Is there any good reason why
| typedef struct resource_entry_t {
| u_long from, num;
^^^^^^
| const char *name;
| struct resource_entry_t *next;
| } resource_entry_t;
while get_ioport_list() uses `%04lx' to print the claimed regions? This makes
me think I should use request_region() for `PC' I/O port regions only.
If we can use request_region() for claiming MMIO, the format specifiers have to
become `%p', so the full 32 (or 64) bit addresses are dumped.
Greetings,
Geert
--
Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium
-
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/