pci.h

missblue · 04-02-2008, 07:27 AM

Hi

I want to use commands like "pci_get_device, pci_resource_start, pci_resource_end,..." to find base address of my IO card. I know pci.h should be included like this: <linux/pci.h>
There's a file with this name in usr/include/linux but the commands are not defined in this header file.
There is also another file with the same name in
usr/src/linux-2.6.../include/linux
the commands are defined in this file.
Could you please tell me how to include this file & all of its dependancies?

osor · 04-02-2008, 08:33 PM

Are you writing kernel code? If so the latter will automatically be in the include path if you use a kernel Makefile to build your source.

missblue · 04-05-2008, 02:28 AM

Thanks for your reply,

I'm using host-target configuration & a software that sends my codes to linux platform then compile them. I don't know exactly what it does but I guess it uses gcc to compile the codes.

osor · 04-05-2008, 07:51 PM

I guess I wasn’t clear. Whatever code makes use of <linux/pci.h> is for a kernel module, it will automatically access the appropriate header when use a kernel makefile. If it is userspace code, it will not have access to the appropriate header.

The userspace version of the header is exactly the same as the kernelspace version, except all declarations armored like so

Code:

#ifdef __KERNEL__

foo;
bar;

#endif /* __KERNEL__ */

should be removed. In that case, even if you could modify your include path to gcc (e.g., “gcc -I/lib/modules/`uname -r`/build/include”) your code would not be able to use the declarations unless it was kernel code.

missblue · 04-06-2008, 02:19 AM

So, is there any way to access PCI Bus (find base address, read & write data) without writing kernel code?

osor · 04-06-2008, 01:50 PM

I don’t think so. But you can access a lot of information about the PCI bus in /proc and /sys. Also, if you want to do port IO, you can read and write to /dev/port (having used lseek to get the appropriate port number). Here is a short document about doing that.

jiml8 · 04-06-2008, 05:17 PM

that is correct. If you don't want to write kernel code, the only information you can get is found in /proc and /sys. Of course, that information is extensive, depending upon the driver that supports the PCI device, but you won't get at the hardware unless you write kernel code.

missblue · 04-08-2008, 12:37 AM

It seems the alternative method(dev/port) is not suitable for realtime performance, is it?
I think I have to write kernel code, could you please give me some information about it?

osor · 04-09-2008, 01:51 PM

Quote:

Originally Posted by missblue

I think I have to write kernel code, could you please give me some information about it?

Consult any linux 2.6 kernel module programming guide.