Next step for libpciaccess

[Ian Romanick]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike A. Harris wrote:
> Ian Romanick wrote:
> 
>> ... The only catch is that libpciaccess
>> uses and external file of PCI IDs.  Right now it assumes that this file
>> is stored /usr/share/hwdata/pci.ids.  I suspect that is not a good
>> assumption to make.  What *is* the right way to locate this file?
> 
> That path is a Red Hat'ism, which might possibly be used by other
> Linux distros also, but I wouldn't assume that per se.

I suspected as much.

> How about testing the OS and distro, and having some defaults for
> certain OS's that can be properly detected, but having a
> --with-pciids-path= option to ./configure to override any autodetection?

I had considered two options, and something like --with-pciids-path was
one of them.  The other was to provide a routine so that the path could
be set at run-time.  Since it seems like at least some systems don't
ship with a pci.ids file at all, we might make that (an optional) part
of either X.org core or libpciaccess.

>> Once the scanpci module is gone (or perhaps before!), the scanpci and
>> pcitweak utilities can be replace with utilities (in util/) that use
>> libpciaccess.  Given the existence of pciutils, I'm actually not
>> convinced that these utilities still have a reason to exist at all.
> 
> I'd agree in general..   Do the pciutils utilities work on other OSs, or
> are they Linux specific?  I've never really checked. ;)

- From the pciutils 2.2.1 README:

	Currently, pciutils work on all versions of Linux and they also
	have somewhat experimental support for FreeBSD, NetBSD, AIX, GNU 	Hurd
and Solaris/x86.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)

iD8DBQFEGubXX1gOwKyEAw8RArkfAJ4rJv2i0rz2tCQIEYKMrn0Q55eopQCdEvpp
KC0T+gBS9Lz/rt4kL4j3lYQ=
=XkAs
-----END PGP SIGNATURE-----