From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: bluez firmware loading
Date: Thu, 07 Apr 2005 19:14:03 +0000 [thread overview]
Message-ID: <1112901243.2095.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050407181758.GA17974@wonderland.linux.it>
On Thu, 2005-04-07 at 20:17 +0200, Marco d'Itri wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug02990
>
> Is this really a bug in the firmware class, or in the bluetooth drivers?
Looks similar to this:
http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m\x111087517321591&w=2
http://marc.theaimsgroup.com/?l=linux-hotplug-devel&m\x111090287820444&w=2
You may include Hannes udev-patch in the meantime, that handles
firmware events different from all others. We will have a TIMEOUT value
in the next kernel and the current devel-udev already recognizes it, but
that will take some time to show up on the users machines.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-04-07 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 18:17 bluez firmware loading Marco d'Itri
2005-04-07 19:05 ` Marcel Holtmann
2005-04-07 19:14 ` Kay Sievers [this message]
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=1112901243.2095.3.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).