From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: how to determine physical bus of a device and find it there
Date: Fri, 23 Jan 2004 01:43:14 +0000 [thread overview]
Message-ID: <20040123014314.GH16052@kroah.com> (raw)
In-Reply-To: <20040120025230.GA26199@vrfy.org>
On Fri, Jan 23, 2004 at 12:42:36AM +0100, Kay Sievers wrote:
> On Thu, Jan 22, 2004 at 02:40:46PM -0800, Greg KH wrote:
> > On Tue, Jan 20, 2004 at 03:52:30AM +0100, Kay Sievers wrote:
> > >
> > > but the really interesting attributes are on the usb bus:
> > > /sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1':
> > >
> > > SYSFS_manufacturer="SMSC"
> > > SYSFS_product="USB 2 Flash Media Device"
> > > SYSFS_serial="0305037000C2"
> > >
> > >
> > > So, how do I reliable get there?
> >
> > We need to set up a "stack" (for lack of a better word) of sysfs
> > devices. We can now do this with some libsysfs calls.
>
> Oh, my english is not quite good, but for me it sounds like a 'chain'?
Yes, that is a much better name for that, thanks.
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-01-23 1:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 2:52 how to determine physical bus of a device and find it there Kay Sievers
2004-01-20 14:09 ` Olaf Hering
2004-01-22 22:40 ` Greg KH
2004-01-22 22:58 ` Greg KH
2004-01-22 23:27 ` Kay Sievers
2004-01-22 23:42 ` Kay Sievers
2004-01-23 1:42 ` Greg KH
2004-01-23 1:43 ` Greg KH [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=20040123014314.GH16052@kroah.com \
--to=greg@kroah.com \
--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.