On Mon, 2005-02-14 at 09:30 -0800, Greg KH wrote: >On Sun, Feb 13, 2005 at 04:14:41AM +0100, Kay Sievers wrote: >> On Tue, 2005-02-08 at 21:53 -0800, Greg KH wrote: >> >On Wed, Feb 09, 2005 at 03:24:31AM +0100, Kay Sievers wrote: >> >> Can't you match against some interface attributes in sysfs, which are >> >> telling you which one is the first interface of this device? >> >> >> >> You may compare: >> >> udevinfo -a -p /class/tty/ttyUSB0 >> >> udevinfo -a -p /class/tty/ttyUSB1 >> >> >> >> if you find a difference between both interfaces to match against, that >> >> is not dependent on the kernel device name. >> > >> >This is a real tough one to try to match on, as these both point to the >> >same exact physical device. Same USB interface even. It's a pain, >> >stupid palm devices... >> >> Ahh, I see. So we may follow the link to the physical device and look >> for the name of the _first_ serial interface of this device? Would this >> solve the problem? > >Heh, not quite, as you usually want the _second_ serial interface to >sync off of, the first one is not useful at all (well, some tools use >it, but 99% of the users never will care about it.) > >And then there's the fun problem of some Sony devices creating two >serial "devices" where the second one is just a "fake" one, and you >really need to connect to the first. > >Bah, sometimes I really hate Palm...
Yeah, I can imagine that. But would it be possible to get the right one with the information available in sysfs? Someone could write a small script which matches the vendor and return a symlink for the _right_ interface. Would that work? Btw: The "Bad parsing ..." wasn't a udev issue. It's solved. Thanks, Kay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
