From: Bernd Porr <berndporr@f2s.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb coldplug problem
Date: Wed, 03 Dec 2008 11:13:32 +0000 [thread overview]
Message-ID: <493669DC.9070907@f2s.com> (raw)
In-Reply-To: <403A9FAC.2010904@free.fr>
I totally take Greg's point that the firmware load should be via a
firmware request from the driver which then in turn triggers the
firmware helper in userspace. When I checked that last time (about a
year ago) this was too buggy and I stuck with the comedi firmware upload
which has been running for about 4 years without probs. Might be a good
time to use the firmware helper.
But in comedi it is so that the command "comedi_config" associates a
driver with a device. This works fine with hotplug. I plug in my usbdux,
this triggers a udev event and then a udev rule can decide which
/dev/comedi? is actaully taking care of the box. If you want to question
that mechanism then comedi itself has to be rewritten. And I'm sure that
nobody here in comedi-land would like to do that. It just works too good.
> Why cannot be the /proc interface be used.
Can you explain that a bit more.
Thanks!
/Bernd
Sujit Karataparambil wrote:
> We need to call the rule in the kernel context as 'greg' was saying.
>
> Seems to be the correct way to be the firmware upload via USB.
>
> On 12/3/08, Kay Sievers <kay.sievers@vrfy.org> wrote:
>> On Wed, Dec 3, 2008 at 09:40, Bernd Porr <berndporr@f2s.com> wrote:
>>
>>>> Yes it will as the startup scripts already know how to handle coldplug
>>>> firmware events.
>>> To give the "magic" a name: you mean udev adm trigger? Or a nice script
>>> which writes "add" to all "uvents"? This is exactly what doesn't work. There
>>> are absolutely no udev events generated for comedi during boot. I've checked
>>> that now thoroughly and I think there's something wrong. What could that be?
>> How does the "device" look like in sysfs, where you want to hook into
>> with the userspace setup?
>>
>> Kay
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
--
www: http://www.berndporr.me.uk/
http://www.linux-usb-daq.co.uk/
http://www.myfriendhelen.org.uk/
Mobile: +44 (0)7840 340069
Work: +44 (0)141 330 5237
University of Glasgow
Department of Electronics & Electrical Engineering
72 Oakfield Avenue (Rankine Building for deliveries)
Glasgow, G12 8LT
next prev parent reply other threads:[~2008-12-03 11:13 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
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 [this message]
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=493669DC.9070907@f2s.com \
--to=berndporr@f2s.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.