From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rule for usb printer
Date: Thu, 22 Jan 2004 15:51:53 +0000 [thread overview]
Message-ID: <20040122155153.GB13767@kroah.com> (raw)
In-Reply-To: <200401211924.08672.bobb@absamail.co.za>
On Thu, Jan 22, 2004 at 10:10:49AM +0200, Bob Barry wrote:
>
> The list is attached. My printer is there, but all that's offered are
> cryptic numbers:
> SYSFS_detach_state="0"
> SYSFS_bInterfaceNumber="00"
> SYSFS_bAlternateSetting=" 0"
> SYSFS_bNumEndpoints="02"
> SYSFS_bInterfaceClass="07"
> SYSFS_bInterfaceSubClass="01"
> SYSFS_bInterfaceProtocol="02"
> SYSFS_iInterface="00"
>
> There's no sign of the "product" I'd found, or of "name" or "model".
> Am I missing something, or misconfigured?
No, you are correct. The "problem" is that usb drivers are bound to usb
interfaces (which is the directory you see above). What you really want
to compare using udev to is the usb device directory, which is one above
this directory. I know about this problem and am working on fixing it
in udev.
Sorry about this...
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
next prev parent reply other threads:[~2004-01-22 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 17:24 udev rule for usb printer Bob Barry
2004-01-21 19:36 ` Kay Sievers
2004-01-22 8:10 ` Bob Barry
2004-01-22 10:04 ` Kay Sievers
2004-01-22 15:51 ` Greg KH [this message]
2004-01-22 20:56 ` Bob Barry
2004-01-27 14:24 ` Bob Barry
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=20040122155153.GB13767@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 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).