When we fail to enable io ports via x86 method, this means
we are a client/nested arbiter. But we still need to enable
io ports that are not in PCI CONF1 range.
---
src/hurd_pci.c | 57 ++
1 file changed, 53 insertions(+), 4 deletions(-)
diff --git
Hi Samuel,
I don't understand how a client/nested arbiter could be currently using these
methods
successfully because the hurd access method would fail to enable io via
x86_enable_io().
That is how we determine if we are a client not a master, by attempting to grab
all io ports and getting rejec
This adds support for ioctls for adding and removing routes in pfinet.
Tested to still access network, but there seems to be a mismatch between
and , I can only make it compile
using the linux header.
---
hurd/iioctl.defs| 17 ++-
hurd/ioctl_types.h | 2 +
pfinet/iioctl-ops.c | 266