Re: firmware path / udev

Thanks for the quick reply. Ok. I'll leave it in the comedilib and add 
the udev there. I'll do it un-versioned.

One question re automake/conf: The problem is the libdir variable. This 
is either /usr/lib or /usr/local/lib. What I would like to have is some 
equivalent of the sysconfdir. Something like syslibdir wich points to 
/lib while libdir, for example, points to /usr/lib. Do you have an idea 
how to resolve that. One option would be to "abuse" libexec for that but 
that won't comply with the automake standard.

/Bernd

www:    http://www.berndporr.me.uk/
         http://www.linux-usb-daq.co.uk/
Mobile: +44 (0)7840 340069
Work:   +44 (0)141 330 5237
         University of Glasgow
         Department of Electronics & Electrical Engineering
         Room 519, Rankine Building, Oakfield Avenue,
         Glasgow, G12 8LT


Frank Mori Hess wrote:
> On Saturday 21 April 2007 11:41, Bernd Porr wrote:
>> I'm looking into the udev/hotplug issue. The convention seems to be for
>> the firware now: /lib/firmware/`uname -r`/driver.
> 
> I googled for /lib/firmware and only found one project that uses that 
> convention?  I'd prefer to just put it an unversioned subdirectory 
> of /lib/firmware by default.  However, since your usbdux stuff is the only 
> open firmware in comedi and the rest was already split out into the 
> comedi_nonfree_firmware tarball, you can do it however you prefer.  
> Another thing to consider is, it's probably slightly easier for a user to 
> build comedilib than the kernel drivers if all they want is an upgraded 
> firmware file.
> 
>> I would suggest to move the actual firmware from comedilib to comedi so
>> that we get also a version-dependent firmware installation in
>> /lib/firmware. The actual udev scripts can stay in comedilib which then
>> load the kernel dependent firmware. This makes it easier to have matched
>> driver/firmware versions.
> 
>

Received on 2007-04-21Z17:01:38