From: Bernd Porr <B.Porr@elec.gla.ac.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb coldplug problem
Date: Mon, 01 Dec 2008 15:21:56 +0000 [thread overview]
Message-ID: <49340114.4000807@elec.gla.ac.uk> (raw)
In-Reply-To: <403A9FAC.2010904@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
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
[-- Attachment #2: B_Porr.vcf --]
[-- Type: text/x-vcard, Size: 386 bytes --]
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@elec.gla.ac.uk
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
next prev parent reply other threads:[~2008-12-01 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 0:49 USB coldplug problem Lionel VICTOR
2008-12-01 8:46 ` usb " Bernd Porr
2008-12-01 14:35 ` Greg KH
2008-12-01 15:21 ` Bernd Porr [this message]
2008-12-01 15:29 ` Greg KH
2008-12-01 18:27 ` Bernd Porr
2008-12-03 6:55 ` Greg KH
2008-12-03 8:40 ` Bernd Porr
2008-12-03 9:18 ` Kay Sievers
2008-12-03 10:28 ` Sujit Karataparambil
2008-12-03 11:13 ` Bernd Porr
2008-12-03 11:46 ` Sujit Karataparambil
2008-12-03 14:59 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49340114.4000807@elec.gla.ac.uk \
--to=b.porr@elec.gla.ac.uk \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).