From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: device not part of a subsystem?
Date: Sat, 09 Apr 2005 00:14:22 +0000 [thread overview]
Message-ID: <1113005662.4771.26.camel@localhost.localdomain> (raw)
In-Reply-To: <20050409000129.GA32481@wonderland.linux.it>
On Sat, 2005-04-09 at 02:01 +0200, Marco d'Itri wrote:
> Is this a bug? The rfcomm driver reports just this:
>
> $ udevinfo -a -p /class/tty/rfcomm0
>
> [...]
>
> device '/sys/class/tty/rfcomm0' has major:minor 216:0
> looking at class device '/sys/class/tty/rfcomm0':
> SYSFS{dev}="216:0"
That looks bad. The subsystem is read from the device path. Don't know
why this isn't working. What udev version is it? Do you use klibc?
How does a "ls -l" in that directory look like?
Is it a bluetooth device?
> Should I change my rules files to not depend on the driver being part of
> the tty subsystem or ask for the rfcomm driver to be fixed?
Hmm, that device should probably have a "device" link? But let's find
the SUBSYSTEM bug first.
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
next prev parent reply other threads:[~2005-04-09 0:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 0:01 device not part of a subsystem? Marco d'Itri
2005-04-09 0:14 ` Kay Sievers [this message]
2005-04-09 0:29 ` Marco d'Itri
2005-04-09 9:20 ` Kay Sievers
2005-04-09 9:22 ` Marco d'Itri
2005-04-09 15:52 ` Marco d'Itri
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=1113005662.4771.26.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 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.