| Summary: | PalmOS USB Device Detection Broken in sys-fs/udev | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sean Smith <seantsmith> |
| Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | 2006.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 126089 | ||
| Attachments: | Patch to udev.rules in udev-087.tar.bz2 | ||
|
Description
Sean Smith
2006-07-24 20:26:30 UTC
Created attachment 92677 [details, diff]
Patch to udev.rules in udev-087.tar.bz2
This patch is to be applied to the udev-087.tar.bz2. It moves the PalmOS lines above the #tty devices line as it is required to utilize the odd numbered ttyUSB devices.
When I ran udevinfo against the sysfs device my Treo 650 created, this was the output:
looking at device '/class/tty/ttyUSB1':
KERNEL=="ttyUSB1"
SUBSYSTEM=="tty"
SYSFS{dev}=="188:1"
looking at device '/devices/pci0000:00/0000:00:10.2/usb3/3-1/3-1.4/3-1.4:1.0/ttyUSB1':
ID=="ttyUSB1"
BUS=="usb-serial"
DRIVER=="visor"
looking at device '/devices/pci0000:00/0000:00:10.2/usb3/3-1/3-1.4/3-1.4:1.0':
ID=="3-1.4:1.0"
BUS=="usb"
DRIVER=="visor"
SYSFS{modalias}=="usb:v0830p0061d0100dc00dsc00dp00icFFisc00ip00"
SYSFS{bInterfaceProtocol}=="00"
SYSFS{bInterfaceSubClass}=="00"
SYSFS{bInterfaceClass}=="ff"
SYSFS{bNumEndpoints}=="04"
SYSFS{bAlternateSetting}==" 0"
SYSFS{bInterfaceNumber}=="00"
looking at device '/devices/pci0000:00/0000:00:10.2/usb3/3-1/3-1.4':
ID=="3-1.4"
BUS=="usb"
DRIVER=="usb"
SYSFS{configuration}==""
SYSFS{serial}=="PalmSN12345678"
SYSFS{product}=="Palm Handheld"
SYSFS{manufacturer}=="PalmOne_ Inc."
SYSFS{maxchild}=="0"
SYSFS{version}==" 1.00"
SYSFS{devnum}=="14"
SYSFS{speed}=="12"
SYSFS{bMaxPacketSize0}=="16"
SYSFS{bNumConfigurations}=="1"
SYSFS{bDeviceProtocol}=="00"
SYSFS{bDeviceSubClass}=="00"
SYSFS{bDeviceClass}=="00"
SYSFS{bcdDevice}=="0100"
SYSFS{idProduct}=="0061"
SYSFS{idVendor}=="0830"
SYSFS{bMaxPower}==" 2mA"
SYSFS{bmAttributes}=="c0"
SYSFS{bConfigurationValue}=="1"
SYSFS{bNumInterfaces}==" 1"
This showed me that the old line 'KERNEL=="pilot", NAME="%k", GROUP="uucp"' would not match properly because KERNEL evaluates out to ttyUSB*. This is why I matched it against 'DRIVER=="visor"' because the driver's not used for anything else. This also should make it generic for any PalmOS based USB organizer.
Also, when the Palm connects to the system, two ttyUSB devices always get created. We need to pick the odd numbered device because that's the one it synchronizes against.
Finally, users who choose to use the pilot will need to be a member of "plugdev."
Sorry, but I can't add this to the generic rules, it breaks other machines with people who have usb - serial devices. My suggestion is just to use a custom rule for your system, as you know what type of device you have, it will work for you. Oh, and it's impossible to create a "generic" rule for all palm devices, sorry. Blame palm for that... |
