Hi!
It's not that easy. The actual udev event triggers comedi_config which
does _also_ the firmware upload on the side. Even if I upload the
firmware via sysfs I still need to run comedi_config to set up the
comedi device. Therefore it's simpler to do it via comedi_config as this
supports firmware upload anyway and people can also do it manually if
udev is not supported, for example on embedded systems. You see I've put
in some thought into that earlier. But I'm open for suggestions. ;-)
/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
72 Oakfield Avenue (for deliveries: Rankine Building)
Glasgow, G12 8LT
Greg KH wrote:
On Mon, Dec 01, 2008 at 08:46:52AM +0000, Bernd Porr wrote:
Hi!
I'm the maintainter of the USBDUX board which connects via the USB to
linux.
In order to work properly the USBDUX needs firmware uploaded. So, I wrote a
udev rule which uploads the firmware as soon as there's a udev event from
the USB BUS (this is done via comedi_config).
Why not just use the firmware functions in the kernel core for this?
That way, when the device is seen by udev, the correct firmware request
function will be called, your firmware will be loaded, and everything
should be just fine.
No need to reinvent the wheel here :)
thanks,
greg k-h
begin:vcard
fn:Bernd Porr
n:Porr;Bernd
org:University of Glasgow;Department of Electronics & Electrical Engineering
adr:Oakfield Avenue;;Room 519, Rankine Building;Glasgow;Scotland;G12 8LT;Scotland
email;internet:b.porr@xxxxxxxxxxxxxx
title:Dr
tel;work:0141 330 5237
tel;fax:0141 330 6004
tel;cell:07840 340069
x-mozilla-html:FALSE
url:http://www.berndporr.me.uk
version:2.1
end:vcard
