From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb endpoint devices
Date: Sun, 13 Aug 2006 17:21:44 +0000 [thread overview]
Message-ID: <1155489704.3321.14.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <20060813170755.GA4408@wonderland.linux.it>
On Sun, 2006-08-13 at 19:07 +0200, Marco d'Itri wrote:
> They are in 2.6.18-rc4, which names should they use?
> What do you think about this rule?
>
> SUBSYSTEM="usb_endpoint", PROGRAM="/bin/sh -c 'K=%k; E=$${K#*_}; K=$${K#usbdev}; K=$${K%%%%_*}; printf bus/usb/%%03i/%%03i_%%s $${K%%%%.*} $${K#*.} $$E'", \
> NAME="%c"
>
>
> DEVNAME='/dev/usbdev1.1_ep81'
> DEVPATH='/devices/pci0000:00/0000:00:10.0/usb1/1-0:1.0/usbdev1.1_ep81'
> SUBSYSTEM='usb_endpoint'
>
> /dev/bus/usb/
> |-- 001
> | |-- 001
> | `-- 001_ep81
They are not functional now, it's work-in-progress. And are you sure,
that this will not confuse libusb access? We should probably leave them
where they are, and not move them into the weird usbfs directory layout.
Kay
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-08-13 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 17:07 usb endpoint devices Marco d'Itri
2006-08-13 17:21 ` Kay Sievers [this message]
2006-08-14 20:50 ` 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=1155489704.3321.14.camel@pim.off.vrfy.org \
--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).