Re: pci config space
Re: pci config space
- Subject: Re: pci config space
- From: Andrew Gallatin <email@hidden>
- Date: Fri, 11 May 2007 08:12:46 -0400 (EDT)
Andrew Gallatin writes:
>
> > My suggestion would be to write a simple driver and communicate with
> > it. That will free you from the availability of the CHUD API.
>
> The problem with this is that the only thing I can visualize will work
> only on x86 (io port access). I can't seem to figure out a way to get
> "random access" to the PCI bus. Eg, I don't see a way specify a
> bus/slot/function and access its PCI config space, even in the kernel.
FWIW, I wrote a trivial kernel extension to allow in/out{b,w,l}, and
our tools are working fine on Intel. Powerpc is still a problem, but
since ppc seems to be pretty much dead, I guess I'll have to not
worry about it.
I would still be interested to know if it is possible somehow to
access PCI device classes on a bus/slot/function bases so I could
use the iokit IOPCIDevice::configRead functions..
Drew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden