Hardware Prob0r

Hello Guys,

I am in the process of creating a bootable CD with my RTLab software on it
ready-to-run.  In the ideal world every person on Earth with a PC with a
DAQ card will be able to pop the CD in and within minutes be running rtlab
which uses Comedi, more or less with little knowledge of linux or comedi.
At any rate, to that end I would like to be able to somehow make the
insmod && comedi_config of comedi modules as painless as possible for
people using my boot cd.  I was thinking of having a complete hardware
list the user picks from and then the cd's bootscripts try the module
associated with that card (passing the right config string to
comedi_config).

As friendly as a menu-driven curses dialog box is, an better approach is
to first try and probe hardware by PCI-ids.  I could scan the PCI bus
(which means that ISA boards aren't probeable) and use the pci-id to try
and auto-load the module (then run comedi_config automatically with the
proper board config string).

This means I need to create a mini-database of a complete list of PCI id's
that comedi supports and relate those id's to human-readable descriptions
of the hardware which should be related to the driver .o file, which
should be related to the string comedi_config expects to receive to
configure the board.  The latter is kind of available off the website as a
hardware list (that hardware link on comedi.org).  The PCI id's are
probably grepable from the source, but still the data needs some
massaging.  Before I go an reinvent the wheel I was wondering if this has
already been done.  Basically my questions are:

1) Apart from grepping through the .c files in the drivers/ directory is
there a complete pci-id list for comedi somewhere?  If not I will compile
such a list and if I do does anyone else need it?

2) Setting PCI-ID's aside for a moment, is there a more up-to-date version
of the hardware database text file?  The one you get when you click on
http://www.comedi.org/hardware.php ?  I noticed this list is incomplete
(for instance _my_ driver isn't there :)  ).  I heard that file is
auto-generated by reading some meta information from the top of each .c
file.. is that script around anywhere?


-Calin

Received on 2003-01-27Z17:03:45