On 23.8.2012 16:28, Ján Veselý wrote: >> We agreed with Jiri that there may be some situations when it may be >> useful to know what kind of a hw resource the driver is passed (for >> example to be able to tell the resources apart), but this is not the >> case. The pio_* interfaces are there to unify the distinct notions of >> I/O ports and memory mapped registers and especially the different >> access mechanisms so that the drivers can be platform neutral and >> portable. Reinforcing the differences in the drivers would be against >> this principle and will also result in non-portable drivers. > > sry to step in this thread. > Maybe we could rename those functions to io_* to make their > universality clearer. > It sure looks ugly accessing mmio resources using something called pio.
Well, PIO does not stand for Port I/O, but for Programmed I/O, to make it clear that we are not talking about DMA I/O. Jakub _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
