PCI lib for 2.4

PCI lib for 2.4

[Damien Couroussé]

Hi all,

I'm a rookie in Linux development, and I have to develop a small driver 
for a data-acquisition card on PCI port.

My problem is that my compiler does not recognize some functions such as 
'pci_resource_start()', or 'pci_find_device()' ...

I used option  'gcc [...] -lpci' in order to link with pci lib, but 
that's not better. It seems that I have many different versions of the  
pci.h file : /usr/src/linux2.4.18-14/include/linux/pci/h is much bigger 
and much more complete, and more interesting (or it seems to be) than my 
/usr/include/linux/pci.h one, or even /usr/include/driver/pci/pci.h one.

If I do a 'locate pci.a', and then a 'grep pci_resource 
filed-returned-by-locate', I do not have anything. That could mean the 
functions I look for do not exist in my lib.

What do I have to do if I wan't to use the .../src/linux2.4.18... one?

Thanks for any help.

Please tell me if linux-kernel list does not directly concern my problem 
or if there others that fit better.

Damien

Re: PCI lib for 2.4

[Martin Mares]

Hi!

> I'm a rookie in Linux development, and I have to develop a small driver 
> for a data-acquisition card on PCI port.
> 
> My problem is that my compiler does not recognize some functions such as 
> 'pci_resource_start()', or 'pci_find_device()' ...

Is your driver a kernel module or a userspace program?

If it's a kernel module, you need to set the right CFLAGS (the same as the
kernel uses).

				Have a nice fortnight
-- 
Martin `MJ' Mares   <mj@ucw.cz>   http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
COBOL -- Completely Outdated, Badly Overused Language

Re: PCI lib for 2.4

[Damien Couroussé]

Hi,

Actually, it will be first a user-space driver.

Maybe I wasn't clear:

I link the PCI library with '-lpci' option, but it seems the library is 
not complete, ie I can't use the whole lib. For example, the compiler 
cannot link pci_resource_start() func. or pci_fond_device(). I think 
these are usually in all pci libraries... My lib does not support dma 
abilities too.

My problem is that I have several pci.h files which contain these 
function (the 'whole package?'), but I don't have the lib that fits 
to...

For example
 >>grep pci_resource_start /usr/lib/pcilib.a
returns nothing. I think it should.

I was just wondering how I will be able to retrieve the good lib, which 
I can't find on my PC.  Tried to update the Red Hat (and kernel), but 
it didn't change anything in my lib. I guess someone installed sthg on 
my PC, which removed the 'good' pci library, or changed it for an other 
lighter version.

Is there anything related with CONFIG_... flags??

Damien

Le dimanche, 14 déc 2003, à 23:40 Europe/Paris, Peter Chubb a écrit :

>>>>>> "Damien" == Damien Courouss <Damien> writes:
>
> Damien> Hi all, I'm a rookie in Linux development, and I have to
> Damien> develop a small driver for a data-acquisition card on PCI
> Damien> port.
>
> Is this a user=space or in-kernel driver?  A user-space driver will
> link with -lpci; an in-kernel driver needs to be built as if part
> of the kernel.
>
> --
> Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT 
> gelato.unsw.edu.au
> The technical we do immediately,  the political takes *forever*
>
  
  

Re: PCI lib for 2.4

[Peter Chubb]

>>>>> "Damien" == Damien Courouss <Damien> writes:

Damien> Hi, Actually, it will be first a user-space driver.

Damien> Maybe I wasn't clear:

The user-space libpci.a has headers in /usr/include/pci/pci.h
Do #include <pci/pci.h> to get at them.
On debian, at least, you need the pciutils-dev package.
Unfortunately, there are no manual pages (yet?)

And *do* look at the example code that comes with libpci.a

pci_resource_start() and so on are kernel functions; you get the same
info in a different way using libpci.a -- Look at the source of lspci
to see what you can do.

(In brief:
        struct pci_access *pacc;
        struct pci_dev *dev;

	pacc = pci_alloc();

        pci_init(pacc);
        pci_scan_bus(pacc);
        for (dev = pacc->devices; dev; dev = dev->next)
        {
                if (dev->vendor_id == PCI_VENDOR_ID_AAA &&
                    dev->device_id == PCI_DEVICE_ID_AAA_BBB)
                    break;
        }
        if (dev == NULL){
                fprintf(stderr, "No AAA BBB device\n");
		exit(1);
	}
        
        pciconf = xmalloc(sizeof *pciconf);
        pciconf->pciconfig.accesstype = PCI_CONFIG;
        pciconf->pciconfig.devp = dev;

        pci_fill_info(dev, PCI_FILL_IDENT | PCI_FILL_BASES | PCI_FILL_IRQ); 

        /*
         * Get the first 64-bytes of config space
         */
        pci_read_block(dev, 0, config, 64);
)

--
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
The technical we do immediately,  the political takes *forever*