From: James Lamanna <jamesl@appliedminds.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Figuring out USB device locations
Date: Thu, 25 Mar 2004 16:33:06 -0800 [thread overview]
Message-ID: <40637A42.4080603@appliedminds.com> (raw)
In-Reply-To: <20040325235740.GA30964@kroah.com>
Greg KH wrote:
> On Thu, Mar 25, 2004 at 09:20:47AM -0800, James Lamanna wrote:
>
>>Is there an easy way to find out what /dev entries usb devices get
>>mapped to from userspace?
>
>
> "easy way" on 2.4? No, sorry. You need 2.6 to determine this in a
> simple manner. But there are some files in the /proc/bus/usb/
> and /proc/bus/input/ directories that will help you out.
Hmm...its not obvious to me how i can use /proc/bus/usb/xxx/yyy to get
the /dev entry information. I can get the USB device number, but I don't
see how to get at a mapping to a major/minor in /dev space (or is this
not possible in 2.4)...
--
James Lamanna
next prev parent reply other threads:[~2004-03-26 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 17:20 Figuring out USB device locations James Lamanna
2004-03-25 23:57 ` Greg KH
2004-03-26 0:33 ` James Lamanna [this message]
2004-03-26 0:41 ` Greg KH
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=40637A42.4080603@appliedminds.com \
--to=jamesl@appliedminds.com \
--cc=greg@kroah.com \
--cc=linux-kernel@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