From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: bt
Date: Mon, 15 Nov 2004 23:11:40 +0000 [thread overview]
Message-ID: <1100560301.7323.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1100558482.3323.23.camel@charis.crosswire.org>
On Mon, 2004-11-15 at 15:41 -0700, Troy A. Griffitts wrote:
> Hey guys, could someone update one or both of these drivers to work with
> the 2.6 kernel. I have just upgraded to FC3 and can't seem to get my
> bluetooth drivers compiled. It would be really great if they could be
> included so I don't have to compile them with every kernel upgrade.
> Here's the bottom line error message I get with the latest attempt.
>
> Nov 15 15:34:41 charis wait_for_sysfs[6207]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/class/bluetooth/hci0'
> properly (no device symlink) or the sysfs-support of your device's
> driver needs to be fixed, please report to <linux-hotplug-
> devel@lists.sourceforge.net>
If your device isn't working, it has nothing to do with this message, it
just means that we miss a symlink to the physical device.
This message will go away with the 2.6.10 kernel as we get in the
environment of the hotplug call what we can expect in sysfs.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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:[~2004-11-15 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 22:41 bt Troy A. Griffitts
2004-11-15 22:56 ` bt Marcel Holtmann
2004-11-15 23:11 ` 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=1100560301.7323.27.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).