From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: empty BUS name
Date: Sun, 09 Jan 2005 15:44:26 +0000 [thread overview]
Message-ID: <1105285466.6565.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050109162724.2fa09e22@inspiron>
On Sun, 2005-01-09 at 16:27 +0100, Alessandro Zummo wrote:
> Hello,
>
> this is the output of udevinfo on my usb printer:
>
> device '/sys/class/usb/lp0' has major:minor 180:0
> looking at class device '/sys/class/usb/lp0':
> SYSFS{dev}="180:0"
>
> follow the class device's "device"
> looking at the device chain at '/sys/devices/pci0000:00/0000:00:1f.2/usb1/1-1/1-1.2/1-1.2:1.0':
> BUS=""
> ID="1-1.2:1.0"
What does:
ls -l /sys/bus/usb/devices/
print?
It works on my box:
[kay@pim ~]$ udevinfo -a -p/sys/class/usb/lp0
device '/sys/class/usb/lp0' has major:minor 180:0
looking at class device '/sys/class/usb/lp0':
SYSFS{dev}="180:0"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1.3/3-1.3:1.0':
BUS="usb"
ID="3-1.3:1.0"
SYSFS{bAlternateSetting}=" 0"
SYSFS{bInterfaceClass}="07"
SYSFS{bInterfaceNumber}="00"
Kay
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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-01-09 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:27 empty BUS name Alessandro Zummo
2005-01-09 15:44 ` Kay Sievers [this message]
2005-01-09 15:56 ` Alessandro Zummo
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=1105285466.6565.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 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.