[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH libpciaccess] hurd: Clients or nested arbiters don't touch io
Re: [PATCH libpciaccess] hurd: Clients or nested arbiters don't touch ioports
Wed, 24 Aug 2022 22:58:00 +0200
Damien Zammit, le mar. 23 août 2022 08:36:56 +0000, a ecrit:
> I tested this patch and linked it to both pci-arbiter.static
> and rumpdisk.static, everything still works.
Did you try Xorg? It uses pci_io_read32 & alike.
> + .open_legacy_io = NULL,
> + .close_io = NULL,
> + .read32 = NULL,
> + .read16 = NULL,
> + .read8 = NULL,
> + .write32 = NULL,
> + .write16 = NULL,
> + .write8 = NULL,
That would break it.
When it was mentioned on IRC, I though this was about an mmio
read/write, which would have to go through PCI drivers etc. since it's
actually i/o ports we just *have* to do ins/outs. Most modern hardware
use mmio, but legacy, e.g. vga/vesa/etc. use these I/O.