Bug#549185: libftdi1: ftdi_sio disconnects FT232RL after bitbanging
tags 549185 moreinfo
thanks
On Tue, Jan 05, 2010 at 04:38:36PM +0100, Aurelien Jarno wrote:
> reassign 549185 linux-2.6
> thanks
>
> On Thu, Oct 01, 2009 at 06:13:51AM -0400, FDi @ r00t3d wrote:
> > Package: libftdi1
> > Version: 0.13-2
> > Severity: normal
> >
> > 1. Hooked the FT232RL to USB
> > [ 1038.709289] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
> > [ 1038.709396] ftdi_sio: Detected FT232RL
> > [ 1038.709509] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
> > [ 1038.714366] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
> > [ 1038.714443] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > [ 1038.714505] usb 1-1: Product: FT245R USB FIFO
> > [ 1038.714560] usb 1-1: Manufacturer: FTDI
> > [ 1038.714615] usb 1-1: SerialNumber: A6005qyc
> >
> > 2. sudo apt-get install libftdi-dev
> >
> > 3. gcc -lftdi -o /usr/share/doc/libftdi-dev/examples/bitbang2 /usr/share/doc/libftdi-dev/examples/bitbang2.c
> >
> > 4. /usr/share/doc/libftdi-dev/examples/bitbang2 -d 1 0x00
> >
> > 5. It works, but this appears in dmesg
> > [ 1046.425463] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
> > [ 1046.425567] ftdi_sio 1-1:1.0: device disconnected
>
> The disconnection at the ftdi_sio level side, is actually normal, as it
> is not possible to have to processes (ftdi_sio and bitbang2) accessing
> the same device. What is not normal is that the device is totally
> disconnected from the USB stack.
>
> This is definitely a kernel issue. Reassigning the bug.
Hi,
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
us whether the problem persists. If so, we should report it upstream
to the kernel.org developers.
The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.
Thanks,
Moritz
Reply to: