From: Arne Ahrend <aahrend@web.de>
To: linux-hotplug@vger.kernel.org
Subject: usblp attributes split in udevinfo
Date: Tue, 13 Feb 2007 22:05:20 +0000 [thread overview]
Message-ID: <20070213230520.64fe8c2b.aahrend@web.de> (raw)
Hi,
lately the relevant attributes for my USB printer udev rule are split over two device
groups in udevinfo output (running udev-103):
looking at device '/class/usb/lp0':
KERNEL="lp0"
SUBSYSTEM="usb"
DRIVER=""
ATTR{dev}="180:0"
looking at parent device '/devices/pci0000:00/0000:00:10.1/usb2/2-2/2-2:1.0':
KERNELS="2-2:1.0"
SUBSYSTEMS="usb"
DRIVERS="usblp"
ATTRS{ieee1284_id}="MFG:Brother_CMD:PCL5,PJL,PCLXL_MDL:HL-1050 series_CLS:PRINTER_"
ATTRS{modalias}="usb:v04F9p0002d0100dc00dsc00dp00ic07isc01ip02"
ATTRS{bInterfaceProtocol}="02"
ATTRS{bInterfaceSubClass}="01"
ATTRS{bInterfaceClass}="07"
ATTRS{bNumEndpoints}="02"
ATTRS{bAlternateSetting}=" 0"
ATTRS{bInterfaceNumber}="00"
[....]
It is not clear to me if this intended (but it does make writing rules for persistent
printer symlinks much harder than it used to be around 2.6.12 or so), or something that
should be fixed in udev or the kernel (I am running 2.6.20 now).
In particular the DRIVER="" for /class/usb/lp0 seems awkward, should it not be usblp? The next group has
DRIVERS="usblp", but a device which is not suitable for printing. Using its ATTRS{modalias} for my udev printer rules
I get symlinks to device nodes like
crw-rw---- 1 root root 254, 14 2007-02-13 18:53 /dev/usbdev2.3_ep82
and not to /dev/usb/lp0.
Can anyone shed some light on this?
Cheers,
Arne
-------------------------------------------------------------------------
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 reply other threads:[~2007-02-13 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 22:05 Arne Ahrend [this message]
2007-02-13 22:10 ` usblp attributes split in udevinfo Kay Sievers
2007-02-13 23:53 ` Arne Ahrend
2007-02-14 0:02 ` Matthias Schwarzott
2007-02-14 7:18 ` Kay Sievers
2007-02-14 17:40 ` Arne Ahrend
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=20070213230520.64fe8c2b.aahrend@web.de \
--to=aahrend@web.de \
--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).