On Mon, Feb 14, 2005 at 07:22:08PM +0100, Kay Sievers wrote: > On Mon, 2005-02-14 at 09:30 -0800, Greg KH wrote: > >> > >> 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?
Yes, if the visor driver exported the type of the port that it was in sysfs (which it does not do right now, never got around to it as my visor is broken...) If anyone wants to take a look into doing this, look at the logic in the drivers/usb/serial/visor.c::palm_os_3_probe() function where it determines the port_function_id type. We should export that info to sysfs, for the os versions that support it. For palm os 4 and greater, I don't know how to get that information, sorry. > Btw: The "Bad parsing ..." wasn't a udev issue. It's solved. Yeah, I think I saw that go by in a bug report. Huge backlog of email today, that's what I get for being sick for 3 days... thanks, greg k-h -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
