Thanks!
On 11/1/06, Greg KH <greg@xxxxxxxxx
> wrote:
On Wed, Nov 01, 2006 at 04:35:27PM -0600, Jes?s Velazquez wrote:
> >Then I would suggest not doing it from within kernel space :)
> >You should be able to do all of this from userspace using libpci, right?
> >You don't need to write kernel code to get to PCI config space for any
> device.
>
> In fact, I tried to do it using libpci but I found some issues. Some
> registers (Extended Configuration Space of PCI Express) are not found using
> libpci (I used the latest). Using libpci, some registers (I'm sure that they
> exists in the current hw) reported 0xfffffffff values, so they look as there
> do not exists. That is why I want to access them from the kernel. I was told
> that those functions rely on the correct low level functions, I mean kernel
> knows when use cfc/cf8 IO ports and when memory mapped registers (using
> ACPI MCFG).
Hm, using libpci should cause the same thing to happen (correct access
modes.) I'd suggest bringing this up with the libpci developers, as you
should not be forced to do this within the kernel.
thanks,
greg k-h
--
Simple Mortal!
