> > Why not simply using bus_space(9) for non-cachable I/O? > > (like sys/arch/arc/arc/bus_space_sparse.c) > > I think the reason for not using was bus space was the lack of an MI > tag for physmem. That said, I don't mind if someone wants to convert > the driver to dance around bus space or do other kinds of maintenance.
I guess bus_space_map(9) + bus_space_vaddr(9) will work, but for now we should put large XXX mark to those functions in MI arch/mips... --- Izumi Tsutsui
