Greg, It turns out "pilot-induced-turbulence" was the cause of the second device not working. It's now working. It seems the Belkin F5U109 will work for us in 2.4.18-3. I'll make sure the "powers-that-be" undertand the kernel we are using needs updating.
Regards, Joel Breazeale > On Tue, Sep 23, 2003 at 04:17:55PM -0500, Joel L. Breazeale wrote: > > Greg, > > > > Thank you for your reply. It's also reassuring to know a bug was actually > > found and *fixed*! 8-) > > > > I have some news. I tried a Belkin F5U109 and it worked, at least for the > > one device I was trying to get working. I did not experience a dropped > > character after 20 trials. Here what I'm seeing in /var/log/messages for > > your information: > > Nice, looks good. > > > I have a follow-up I hope you can comment upon. Now that it seems the first > > device works and doesn't drop characters, I have one other device that I'd > > like to see if I can get working (but it's not crucial) with the same adapter. > > I'm forced to use the adapter as the target laptop only has one serial port. > > The second device works fine with /dev/ttyS0. Should the code that works with > > the serial port be able to work unchanged with /dev/ttyUSB0? My guess is that > > it should. The current code sets line speed (B19200) and mode (CS7 | CLOCAL | > > CREAD | PARENB), all that serial stuff you would expect; may I presume the com- > > bination of serial-to-USB adapter and driver should cause the adapter to be re- > > configured to use the correct serial settings? > > Yes, it should all "just work". Just point your program to > /dev/ttyUSB0. > > > If all of this is true then it's curious that this just doesn't work. > > Perhaps I've found a problem. I would be glad to pursue it if it > > would ultimately help to shore up a bug. If you can give me any > > pointers on proceeding on debugging this situation I would be glad to > > try. It might be useful to know the devide in question only trans- > > mits data. > > What is not working? Some usb-serial drivers do not handle all of the > different serial ioctls (don't know about this driver, as I didn't write > it.) For example, the "setserial" program will not work on most > usb-serial drivers (the io_edgeport and io_ti drivers being the > exception). > > thanks, > > greg k-h > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
