On Mon, 9 Aug 2010, Dave Mielke wrote: > [quoted lines by Alan Stern on 2010/08/07 at 16:50 -0400] > > >It would help to see a usbmon trace showing the problem, preferably > >from a 2.6.35 kernel. > > Okay, the user got one for us. It's attached to this message (as > usbmon1u.34.gz). The kernel he used is 2.6.35-rc6-686 (Debian Experimental). > > lsusb lists the device as follows: > > Bus 001 Device 005: ID 0403:6001 Future Technology Devices > International, Ltd FT232 USB-Serial (UART) IC > > He chose to cat 1u since lsusb reported "bus 001". > > He did the following: > > 1) Stop brltty and disconnect the adapter. > 2) Start catting 1u. > 3) Connect the adapter. > 4) Start brltty. > 5) echo \002\033b >/devttyUsb0 > 6) Wait for the braille display to start functioning normally. > 7) Stop catting 1u. > > Note that after 4 (starting brltty), the braille display didn't work as it > should. Only after 5 (echoing that byte sequence to it) did the braille display > start working properly. The byte sequence is a valid one which the device > recognizes, and also which the driver would've already sent, which seems to be > what it takes to synchronize the data toggles (assuming my theory is correct). I'm busy now with LinuxCon; I'll try to look at this next week. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
