>I/O is not supposed to be fast, that's what MMIO is for. :) Just do > >void outb (u8 val, u16 addr) >{ > void *addr = ioremap (ISA_IO_BASE + addr); > if (addr) { > writeb (val, addr); > iounmap (addr); > } >} > >You can map and unmap for each call :) Ugly and slow, but hey, it's >I/O... Well, that would really suck ;) And I don't think it would be necessary as we can probably limit each IO bus to 64k without much problem, and have them permanently ioremap'ed. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: The IO problem on multiple PCI... David S. Miller
- Re: The IO problem on multipl... Benjamin Herrenschmidt
- Re: The IO problem on mul... David S. Miller
- Re: The IO problem on multiple PCI busses Benjamin Herrenschmidt
- Re: The IO problem on multiple PCI busses David S. Miller
- Re: The IO problem on multiple PCI bus... Alan Cox
- Re: The IO problem on multiple PCI bus... Benjamin Herrenschmidt
- Re: The IO problem on multiple PCI... David S. Miller
- Re: The IO problem on multipl... Benjamin Herrenschmidt
- Re: The IO problem on mul... Jeff Garzik
- Re: The IO problem on mul... Benjamin Herrenschmidt
- Re: The IO problem on mul... David Woodhouse
- Re: The IO problem on multipl... Oliver Xymoron
- Re: The IO problem on mul... Tony Mantler
- Re: The IO problem on multiple PCI busses Grant Grundler
- Re: The IO problem on multiple PCI busses David S. Miller
- Re: The IO problem on multiple PCI busses Grant Grundler