From: David Dillow <dave@thedillows.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Michael Brown <mebrown@michaels-house.net>,
Doug Warzecha <Douglas_Warzecha@dell.com>,
Jean Delvare <khali@linux-fr.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Matt Domsch <Matt_Domsch@dell.com>
Subject: Re: Class device namespaces
Date: Thu, 30 Apr 2009 11:18:04 -0400 [thread overview]
Message-ID: <1241104684.26576.4.camel@lap75545.ornl.gov> (raw)
In-Reply-To: <ac3eb2510904291453p4c4ec456u1efd7bc6bbf8f3be@mail.gmail.com>
On Wed, 2009-04-29 at 23:53 +0200, Kay Sievers wrote:
> On Wed, Apr 29, 2009 at 23:28, Michael Brown <mebrown@michaels-house.net> wrote:
> > I cant say that I've ever seen any problems due to udev
> > cancelling a firmware request. In fact, if I manually trigger a
> > request using "echo" from the cmdline, I dont see udev take any action
> > with the dell_rbu device. eg (Fedora 10, udev-127-5.fc10):
>
> If you run:
> udevmonitor --udev --env
> at the same time, what does it say?
>
> > I dont see any of the behaviour that you have talked about. If I let
> > it sit there for hours, it will stay at that state. It only closes up
> > the request_firmware() request when I echo 0 > loading.
>
> Udev will run in the moment this sysfs device is created, and it
> should trigger the removal of the device, if it does not find the
> requested firmware file.
drivers/firmware/dell_rbu.c does this:
req_firm_rc = request_firmware_nowait(THIS_MODULE,
FW_ACTION_NOHOTPLUG, "dell_rbu",
&rbu_device->dev, &context,
callbackfn_rbu);
I've not gone looking to verify, but FW_ACTION_NOHOTPLUG implies to me
that udev never sees a uevent for it.
next prev parent reply other threads:[~2009-04-30 16:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 15:48 Class device namespaces Jean Delvare
2009-03-29 16:36 ` Kay Sievers
2009-03-30 8:49 ` Jean Delvare
2009-03-30 11:24 ` Kay Sievers
2009-04-26 6:54 ` Jean Delvare
2009-04-26 12:44 ` Matt Domsch
2009-04-26 13:01 ` Matt Domsch
2009-04-27 15:30 ` Jean Delvare
2009-04-27 17:30 ` Matt Domsch
2009-04-26 13:42 ` Kay Sievers
2009-04-27 16:00 ` Jean Delvare
2009-04-27 21:57 ` Kay Sievers
2009-04-28 8:08 ` Jean Delvare
2009-04-28 12:36 ` Kay Sievers
2009-04-29 12:19 ` Jean Delvare
2009-04-27 13:20 ` Michael E Brown
2009-04-27 15:27 ` Jean Delvare
2009-04-27 17:23 ` Michael Brown
2009-04-28 8:10 ` Jean Delvare
2009-04-28 17:39 ` Doug Warzecha
2009-04-28 17:46 ` Kay Sievers
2009-04-28 21:58 ` Doug Warzecha
2009-04-29 1:42 ` Kay Sievers
2009-04-29 3:19 ` Michael Brown
2009-04-29 10:30 ` Kay Sievers
2009-04-29 17:00 ` Michael Brown
2009-04-29 19:10 ` Kay Sievers
2009-04-29 21:28 ` Michael Brown
2009-04-29 21:53 ` Kay Sievers
2009-04-30 15:18 ` David Dillow [this message]
2009-04-30 16:34 ` Kay Sievers
2009-04-28 19:06 ` Jean Delvare
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=1241104684.26576.4.camel@lap75545.ornl.gov \
--to=dave@thedillows.org \
--cc=Douglas_Warzecha@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mebrown@michaels-house.net \
/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.