devans477
October 9th, 2004, 04:15 PM
Hi,
I am using WRITE_PORT_ULONG and READ_PORT_ULONG to get information from the PCI configuration space. First I write to port 0xCF8 a structure that points to the register I want access. Then I read port 0xCFC to retrieve the register value.
The problem:
Applications that use the same technique to obtain PCI information, conflict with my driver when run concurrently on my hyper-threaded workstation. My driver performs a WRITE_PORT_ULONG, but then another driver performs a WRITE_PORT_ULONG before my driver performs its READ_PORT_ULONG.
Is there any way to protect the read/write operation or reserve the ports for a brief period?
Any help is appreciated.
I am using WRITE_PORT_ULONG and READ_PORT_ULONG to get information from the PCI configuration space. First I write to port 0xCF8 a structure that points to the register I want access. Then I read port 0xCFC to retrieve the register value.
The problem:
Applications that use the same technique to obtain PCI information, conflict with my driver when run concurrently on my hyper-threaded workstation. My driver performs a WRITE_PORT_ULONG, but then another driver performs a WRITE_PORT_ULONG before my driver performs its READ_PORT_ULONG.
Is there any way to protect the read/write operation or reserve the ports for a brief period?
Any help is appreciated.