ftdi-usb-sio-devel Mailing List for FTDI USB Serial Converter Driver (Page 7)
Brought to you by:
bryder
Menu
▾
▴
ftdi-usb-sio-devel — FTDI USB Device Driver development discussion list
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(11) |
Nov
(25) |
Dec
(25) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(16) |
Feb
(98) |
Mar
(46) |
Apr
(35) |
May
(15) |
Jun
(73) |
Jul
(49) |
Aug
(28) |
Sep
(16) |
Oct
(24) |
Nov
(36) |
Dec
(37) |
| 2004 |
Jan
(40) |
Feb
(21) |
Mar
(32) |
Apr
(27) |
May
(32) |
Jun
(48) |
Jul
(62) |
Aug
(22) |
Sep
(13) |
Oct
(14) |
Nov
(24) |
Dec
(26) |
| 2005 |
Jan
(15) |
Feb
(14) |
Mar
(31) |
Apr
(19) |
May
(23) |
Jun
(76) |
Jul
(64) |
Aug
(68) |
Sep
(30) |
Oct
(11) |
Nov
(20) |
Dec
(14) |
| 2006 |
Jan
(7) |
Feb
(5) |
Mar
(10) |
Apr
(10) |
May
(17) |
Jun
(13) |
Jul
(9) |
Aug
(8) |
Sep
(27) |
Oct
(54) |
Nov
(38) |
Dec
(31) |
| 2007 |
Jan
(21) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
(3) |
Jun
(2) |
Jul
(2) |
Aug
(11) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
|
| 2008 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
(8) |
Sep
|
Oct
(3) |
Nov
(6) |
Dec
(2) |
| 2009 |
Jan
(14) |
Feb
(3) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(5) |
Dec
(6) |
| 2010 |
Jan
(3) |
Feb
(5) |
Mar
(2) |
Apr
(4) |
May
(1) |
Jun
(7) |
Jul
(7) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(15) |
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
(3) |
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Syed A. G. <am...@sy...> - 2008-08-14 08:34:07
|
I have a bunch of FT232BL here which is the lead free versions of the FT232BM. They have a
different bcdDevice version then the kernel driver expects:
ftdi_determine_type: bcdDevice = 0x200, bNumInterfaces = 1
With that Version they are detected as FT8U232AM which does not work. When I force them to be
detected as FT232BM they work fine.
So now I'm not sure how to change the detection routine, without breaking detection for the
other chips.
This would work:
--- ftdi_sio.c.orig 2008-08-14 10:18:40.000000000 +0200
+++ ftdi_sio.c 2008-08-14 10:21:16.000000000 +0200
@@ -825,6 +825,9 @@
dbg("%s: something fishy - bcdDevice too low for multi interface
device",
__FUNCTION__);
}
+ } else if (version == 0x200) {
+ // Assume its an FT232BL (lead free version of FT232BM)
+ priv->chip_type = FT232BM;
} else if (version < 0x200) {
/* Old device. Assume its the original SIO. */
priv->chip_type = SIO;
But since I did not found a list of all bcdDevice for all ftdi chips, I don't know if there is
a FT8U232AM with the same bcdDevice and I need to make a complete different detection.
|
|
From: Christophe L. <chr...@gm...> - 2008-06-10 17:07:06
|
Well, good news, it seems it was an issue in my kernel. I made a rebuilt of the kernel and I changed some options on the USB and I didn't update the module and the insmod at the boot. Now the device is recognized. Thanks 2008/6/9 Bill Ryder <bil...@gm...>: > That is strange. > > I'd be inclined to rmmod the ftdi module and reload it. > > It would be a usb bug but if you have the ftdi plugged into a hub try it > without using the hub. > > |
|
From: Bill R. <bil...@gm...> - 2008-06-09 20:00:42
|
That is strange. I'd be inclined to rmmod the ftdi module and reload it. It would be a usb bug but if you have the ftdi plugged into a hub try it without using the hub. On Sat, Jun 7, 2008 at 10:41 PM, Christophe Lindheimer < chr...@gm...> wrote: > Hello > > Just newbie in using FTDI. > > I have just compiled a "Linux gp2x 2.4.25" including the FTDI driver. > > Starting kernel ... > usb.c: registered new driver hub > usb.c: registered new driver serial > usbserial.c: USB Serial Driver core v1.4 > usbserial.c: USB Serial support registered for FTDI SIO > usbserial.c: USB Serial support registered for FTDI 8U232AM Compatible > usbserial.c: USB Serial support registered for FTDI FT232BM Compatible > usbserial.c: USB Serial support registered for USB-UIRT Infrared > Receiver/Transmitter > usbserial.c: USB Serial support registered for Home-Electronics TIRA-1 IR > Transceiver > ftdi_sio.c: v1.3.5:USB FTDI Serial Converters Driver > > > During the boot it looks OK. > > When I plug into the USB, I get > usb.c: USB device 5 (vend/prod 0x403/0x6001) is not claimed by any active > driver. > > Looking at the code it seems to me that (vend/prod 0x403/0x6001) should be > OK for the driver ... > > Any ideas ? > > Thanks > > > > hub.c: new USB device <NULL>-1.3, assigned address 5 > Manufacturer: FTDI > Product: US232B > SerialNumber: FTAJMR92 > usb.c: USB device 5 (vend/prod 0x403/0x6001) is not claimed by any active > driver. > Length = 18 > DescriptorType = 01 > USB version = 1.10 > Vendor:Product = 0403:6001 > MaxPacketSize0 = 8 > NumConfigurations = 1 > Device version = 4.00 > Device Class:SubClass:Protocol = 00:00:00 > Per-interface classes > Configuration: > bLength = 9 > bDescriptorType = 02 > wTotalLength = 0020 > bNumInterfaces = 01 > bConfigurationValue = 01 > iConfiguration = 00 > bmAttributes = a0 > MaxPower = 44mA > > Interface: 0 > Alternate Setting: 0 > bLength = 9 > bDescriptorType = 04 > bInterfaceNumber = 00 > bAlternateSetting = 00 > bNumEndpoints = 02 > bInterface Class:SubClass:Protocol = ff:ff:ff > iInterface = 02 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 81 (in) > bmAttributes = 02 (Bulk) > wMaxPacketSize = 0040 > bInterval = 00 > Endpoint: > bLength = 7 > bDescriptorType = 05 > bEndpointAddress = 02 (out) > bmAttributes = 02 (Bulk) > wMaxPacketSize = 0040 > bInterval = 00 > kusbd_policy: /sbin/hotplug add 5, ret=0x0 > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Ftdi-usb-sio-devel mailing list > Ftd...@li... > https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel > > |
|
From: Christophe L. <chr...@gm...> - 2008-06-07 10:41:38
|
Hello
Just newbie in using FTDI.
I have just compiled a "Linux gp2x 2.4.25" including the FTDI driver.
Starting kernel ...
usb.c: registered new driver hub
usb.c: registered new driver serial
usbserial.c: USB Serial Driver core v1.4
usbserial.c: USB Serial support registered for FTDI SIO
usbserial.c: USB Serial support registered for FTDI 8U232AM Compatible
usbserial.c: USB Serial support registered for FTDI FT232BM Compatible
usbserial.c: USB Serial support registered for USB-UIRT Infrared
Receiver/Transmitter
usbserial.c: USB Serial support registered for Home-Electronics TIRA-1 IR
Transceiver
ftdi_sio.c: v1.3.5:USB FTDI Serial Converters Driver
During the boot it looks OK.
When I plug into the USB, I get
usb.c: USB device 5 (vend/prod 0x403/0x6001) is not claimed by any active
driver.
Looking at the code it seems to me that (vend/prod 0x403/0x6001) should be
OK for the driver ...
Any ideas ?
Thanks
hub.c: new USB device <NULL>-1.3, assigned address 5
Manufacturer: FTDI
Product: US232B
SerialNumber: FTAJMR92
usb.c: USB device 5 (vend/prod 0x403/0x6001) is not claimed by any active
driver.
Length = 18
DescriptorType = 01
USB version = 1.10
Vendor:Product = 0403:6001
MaxPacketSize0 = 8
NumConfigurations = 1
Device version = 4.00
Device Class:SubClass:Protocol = 00:00:00
Per-interface classes
Configuration:
bLength = 9
bDescriptorType = 02
wTotalLength = 0020
bNumInterfaces = 01
bConfigurationValue = 01
iConfiguration = 00
bmAttributes = a0
MaxPower = 44mA
Interface: 0
Alternate Setting: 0
bLength = 9
bDescriptorType = 04
bInterfaceNumber = 00
bAlternateSetting = 00
bNumEndpoints = 02
bInterface Class:SubClass:Protocol = ff:ff:ff
iInterface = 02
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 81 (in)
bmAttributes = 02 (Bulk)
wMaxPacketSize = 0040
bInterval = 00
Endpoint:
bLength = 7
bDescriptorType = 05
bEndpointAddress = 02 (out)
bmAttributes = 02 (Bulk)
wMaxPacketSize = 0040
bInterval = 00
kusbd_policy: /sbin/hotplug add 5, ret=0x0
|
|
From: Craig V. D. <cr...@yo...> - 2008-03-18 04:06:27
|
Martin, It sounds like the same problems I dealt with when using two DLP-2232PB-G boards. You may find the code and discussion at http://yosemitefoothills.com/Electronics/index.html and http://yosemitefoothills.com/Electronics/FOSUG.html useful. In particular, the discussion of binding and unbinding to the serial drivers and the routine I needed to control the binding. Craig On Monday 17 March 2008 12:42:15 Martin Gramatke wrote: > Hello, > > I have two ftdi devices from different manufacturers. Whenever I plug in > the second (ttyUSB1) the first becomes disconnected (ttyUSB0). What is > wrong? > > snippet from /var/log/messages: > Mar 16 21:17:38 lab2 kernel: usb 5-2: new full speed USB device using > ohci_hcd and address 2 > Mar 16 21:17:38 lab2 kernel: usb 5-2: configuration #1 chosen from 1 choice > Mar 16 21:17:38 lab2 kernel: ftdi_sio 5-2:1.0: FTDI USB Serial Device > converter detected > Mar 16 21:17:38 lab2 kernel: drivers/usb/serial/ftdi_sio.c: Detected > FT8U232AM Mar 16 21:17:38 lab2 kernel: usb 5-2: FTDI USB Serial Device > converter now attached to ttyUSB1 > Mar 16 21:19:47 lab2 kernel: usb 2-2: reset full speed USB device using > ohci_hcd and address 2 > Mar 16 21:19:47 lab2 kernel: ftdi_sio 2-2:1.0: device disconnected > Mar 16 21:19:47 lab2 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device > converter now disconnected from ttyUSB0 > Mar 16 21:21:58 lab2 kernel: usb 2-2: reset full speed USB device using > ohci_hcd and address 2 > > regards > Martin > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Ftdi-usb-sio-devel mailing list > Ftd...@li... > https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel |
|
From: Martin G. <xm...@gm...> - 2008-03-17 19:42:22
|
Hello, I have two ftdi devices from different manufacturers. Whenever I plug in the second (ttyUSB1) the first becomes disconnected (ttyUSB0). What is wrong? snippet from /var/log/messages: Mar 16 21:17:38 lab2 kernel: usb 5-2: new full speed USB device using ohci_hcd and address 2 Mar 16 21:17:38 lab2 kernel: usb 5-2: configuration #1 chosen from 1 choice Mar 16 21:17:38 lab2 kernel: ftdi_sio 5-2:1.0: FTDI USB Serial Device converter detected Mar 16 21:17:38 lab2 kernel: drivers/usb/serial/ftdi_sio.c: Detected FT8U232AM Mar 16 21:17:38 lab2 kernel: usb 5-2: FTDI USB Serial Device converter now attached to ttyUSB1 Mar 16 21:19:47 lab2 kernel: usb 2-2: reset full speed USB device using ohci_hcd and address 2 Mar 16 21:19:47 lab2 kernel: ftdi_sio 2-2:1.0: device disconnected Mar 16 21:19:47 lab2 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Mar 16 21:21:58 lab2 kernel: usb 2-2: reset full speed USB device using ohci_hcd and address 2 regards Martin |
|
From: <ari...@gm...> - 2008-01-19 20:29:21
|
I have a CableStar 2 PCI DVB-C card with remote module.
When I attach the remote module (IR-receiver) to my
serial port it works OK with VDR using lirc.
I bought an usb2serial converter (FT232BM based) and
can't get my remote working with lirc at all. :(
Converter is recognized as:
Bus 002 Device 004: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
I think it fails with ioctl call below:
ftdi_sio.c: ftdi_ioctl cmd 0x80046900
ftdi_sio.c: ftdi_ioctl arg not supported - it was 0x80046900 - check
/usr/include/asm/ioctls.h
I tried to gather as much info as I could below.
Maybe someone can help me to get the converter working.
I really need more than only one serial port...
--
# uname -a
Linux dell.localdomain 2.6.22.14-72.fc6 #1 SMP Wed Nov 21 15:12:59 EST 2007
i686 i686 i386 GNU/Linux
--
# /usr/sbin/lircd -n -H default -d /dev/ttyUSB0 --nodaemon /etc/lircd.conf
lircd-0.8.1[7481]: lircd(userspace) ready
lircd-0.8.1[7481]: accepted new client on /dev/lircd
lircd-0.8.1[7481]: could not get hardware features
lircd-0.8.1[7481]: this device driver does not support the new LIRC interface
lircd-0.8.1[7481]: major number of /dev/ttyUSB0 is 188
lircd-0.8.1[7481]: LIRC major number is 61
lircd-0.8.1[7481]: check if /dev/ttyUSB0 is a LIRC device
lircd-0.8.1[7481]: caught signal
Terminated
--
FC6 2.6.22.14-72.fc6 w/ native ftdi_sio (from FC6) driver:
Kernel messages w/ above driver:
Jan 16 22:04:02 dell kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for FTDI USB Serial Device
Jan 16 22:04:02 dell kernel: ftdi_sio 2-2:1.0: FTDI USB Serial Device
converter detected
Jan 16 22:04:02 dell kernel: drivers/usb/serial/ftdi_sio.c: Detected FT232BM
Jan 16 22:04:02 dell kernel: usb 2-2: FTDI USB Serial Device converter
now attached to ttyUSB0
Jan 16 22:04:02 dell kernel: usbcore: registered new interface driver ftdi_sio
Jan 16 22:04:02 dell kernel: drivers/usb/serial/ftdi_sio.c: v1.4.3:USB
FTDI Serial Converters Driver
Jan 16 22:04:02 dell kernel: lirc_dev: IR Remote Control driver
registered, major 61
Jan 16 22:04:02 dell kernel: lirc_serial: no version for "lirc_unregister_plugin
" found: kernel tainted.
Jan 16 22:04:02 dell kernel: lirc_serial: auto-detected active low receiver
Jan 16 22:04:02 dell kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
FC6 2.6.22.14-72.fc6 w/ native ftdi_sio (from FC6) driver:
Driver debug messages when I try to connect to lirc w/ irw:
ftdi_sio.c: ftdi_open
ftdi_sio.c: ftdi_set_termios
ftdi_sio.c: Setting CS8
ftdi_sio.c: get_ftdi_divisor - tty_get_baud_rate reports speed 9600
ftdi_sio.c: get_ftdi_divisor - Baud rate set to 9600 (divisor 0x4138)
on chip FT232BM
ftdi_sio.c: update_mctrl - DTR HIGH, RTS HIGH
ftdi_sio.c: ftdi_set_termios Turning off hardware flow control
ftdi_sio.c: update_mctrl - DTR HIGH, RTS HIGH
ftdi_sio.c: ftdi_ioctl cmd 0x80046900
ftdi_sio.c: ftdi_ioctl arg not supported - it was 0x80046900 - check
/usr/include/asm/ioctls.h
ftdi_sio.c: ftdi_close
ftdi_sio.c: ftdi_read_bulk_callback - port 0
ftdi_sio.c: update_mctrl - DTR LOW, RTS LOW
--
I tried also with newer driver.
FC6 2.6.22.14-72.fc6 w/ ftdi_sio driver from linux kernel 2.16.23.14:
Driver debug messages when I try to connect to lirc w/ irw:
ftdi_sio.c: ftdi_open
ftdi_sio.c: ftdi_set_termios
ftdi_sio.c: Setting CS8
ftdi_sio.c: get_ftdi_divisor - tty_get_baud_rate reports speed 9600
ftdi_sio.c: get_ftdi_divisor - Baud rate set to 9600 (divisor 0x4138)
on chip FT232BM
ftdi_sio.c: update_mctrl - DTR HIGH, RTS HIGH
ftdi_sio.c: ftdi_set_termios Turning off hardware flow control
ftdi_sio.c: update_mctrl - DTR HIGH, RTS HIGH
ftdi_sio.c: ftdi_ioctl cmd 0x80046900
ftdi_sio.c: ftdi_ioctl arg not supported - it was 0x80046900 - check
/usr/include/asm/ioctls.h
ftdi_sio.c: ftdi_read_bulk_callback - port 0
ftdi_sio.c: ftdi_process_read - port 0
ftdi_sio.c: Status only: 261o 140o
ftdi_sio.c: ftdi_read_bulk_callback - port 0
ftdi_sio.c: ftdi_process_read - port 0
ftdi_sio.c: Status only: 261o 140o
ftdi_sio.c: ftdi_read_bulk_callback - port 0
ftdi_sio.c: ftdi_process_read - port 0
ftdi_sio.c: Status only: 261o 140o
ftdi_sio.c: ftdi_read_bulk_callback - port 0
ftdi_sio.c: ftdi_process_read - port 0
ftdi_sio.c: Status only: 261o 140o
ftdi_sio.c: ftdi_close
ftdi_sio.c: update_mctrl - DTR LOW, RTS LOW
ftdi_sio.c: ftdi_read_bulk_callback - port 0
----
# lsusb -v
Bus 002 Device 004: ID 0403:6001 Future Technology Devices
International, Ltd 8-bit FIFO
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 8-bit FIFO
bcdDevice 4.00
iManufacturer 1 FTDI
iProduct 2 USB <-> Serial
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 USB <-> Serial
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
---
# lsmod
Module Size Used by
lirc_serial 17940 0
lirc_dev 18804 1 lirc_serial
ftdi_sio 37384 0
nfsd 208817 17
exportfs 9537 1 nfsd
autofs4 24773 2
eeprom 11345 0
hidp 26689 2
nfs 229037 1
lockd 64457 3 nfsd,nfs
nfs_acl 7617 2 nfsd,nfs
rfcomm 44377 0
l2cap 30401 10 hidp,rfcomm
bluetooth 57893 5 hidp,rfcomm,l2cap
sunrpc 161981 13 nfsd,nfs,lockd,nfs_acl
ipv6 278085 28
dm_multipath 21961 0
video 20937 0
sbs 22729 0
button 12113 0
dock 13921 0
battery 14149 0
ac 9285 0
lp 16105 0
stv0297 11329 2
bcm3510 13381 0
lgdt330x 12229 0
snd_intel8x0 36061 0
nxt200x 17093 0
snd_ac97_codec 96613 1 snd_intel8x0
ac97_bus 6465 1 snd_ac97_codec
snd_seq_dummy 7877 0
mt352 10181 0
snd_seq_oss 33473 0
snd_seq_midi_event 11073 1 snd_seq_oss
snd_seq 50609 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
dvb_ttpci 97801 6
snd_seq_device 11981 3 snd_seq_dummy,snd_seq_oss,snd_seq
stv0299 13897 0
saa7146_vv 49345 1 dvb_ttpci
snd_pcm_oss 43457 0
snd_mixer_oss 19521 1 snd_pcm_oss
video_buf 27717 1 saa7146_vv
saa7146 22857 2 dvb_ttpci,saa7146_vv
snd_pcm 74949 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
b2c2_flexcop_pci 12377 14
b2c2_flexcop 29773 1 b2c2_flexcop_pci
videodev 30785 1 saa7146_vv
v4l2_common 20801 2 saa7146_vv,videodev
iTCO_wdt 14693 0
snd_timer 24901 2 snd_seq,snd_pcm
v4l1_compat 17349 2 saa7146_vv,videodev
dvb_core 78953 4 lgdt330x,dvb_ttpci,stv0299,b2c2_flexcop
iTCO_vendor_support 7877 1 iTCO_wdt
snd 53317 9
snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
i2c_i801 12369 0
ttpci_eeprom 6593 1 dvb_ttpci
soundcore 11681 1 snd
dvb_pll 18245 1 b2c2_flexcop
floppy 58661 0
snd_page_alloc 14281 2 snd_intel8x0,snd_pcm
ide_cd 40545 0
i2c_core 27841 12
eeprom,stv0297,bcm3510,lgdt330x,nxt200x,mt352,dvb_ttpci,stv0299,b2c2_flexcop,i2c_i801,ttpci_eeprom,dvb_pll
usbserial 35625 1 ftdi_sio
cdrom 37089 1 ide_cd
parport_pc 30821 1
e1000 118401 0
parport 38281 2 lp,parport_pc
serio_raw 10821 0
dm_snapshot 21093 0
dm_zero 6208 0
dm_mirror 25153 0
dm_mod 56833 13 dm_multipath,dm_snapshot,dm_zero,dm_mirror
ata_piix 18757 0
libata 120881 1 ata_piix
sd_mod 31297 0
scsi_mod 140621 2 libata,sd_mod
ext3 125641 4
jbd 59881 1 ext3
mbcache 12485 1 ext3
ehci_hcd 35661 0
ohci_hcd 23877 0
uhci_hcd 27089 0
---
Thank you. Sorry for a lengthy post.
|
|
From: David K. <da...@th...> - 2008-01-12 05:24:03
|
Peter Shtinkov said > I Had the same problem. > In fact when driver is cleaned up in version 1.4.3 the quirks for > USB-UIRT and HE-TIRA1 are executed before common initialization and > that's why they writes to pointer which points to NULL. I have written > this patch in order to get these devices to work. I have USB-UIRT and > some other device and both of them are using driver ftdi_sio. > With this patch both devices are working perfectly. > I have no HE-TIRA1 to see if patch works for that device. > If you find it useful please forward it to kernel maintainer for this > driver. > > Regards! Has this ever been fixed, or is there a plan to? I have a USB-UIRT I'm trying to hook up to my Fedora 8 box with a 2.6.23 kernel, but it looks like this problem existed back in the 2.6.20 kernel, too. I just subscribed to this list just now to work on this problem, so sorry if I missed a previous post that covers this. Thanks. Oh, just to reiterate, the symptom looks like: lircd: tty_setdtr: ioctl(TIOCMGET) failed lircd: tty_setdtr: Bad address with debugging on, and lircd-0.8.2[10913]: lircd(userspace) ready lircd-0.8.2[10913]: accepted new client on /dev/lircd lircd-0.8.2[10913]: uirt2_raw: checksum error lircd-0.8.2[10913]: uirt2_raw: UIRT version 0905 ok lircd-0.8.2[10913]: uirt2_raw: could not set DTR lircd-0.8.2[10913]: caught signal with debugging off. |
|
From: Dustin O. <do...@in...> - 2007-11-30 20:03:41
|
I was wondering if anyone has had a problem communicating with the 245R? I'm trying to port some Windows code to Linux, and nothing is working to get a response from this device. I have some 232 code that I now works for Linux, which isn't working either. It's my understanding that to see status messages, I need to turn on communication with the device. How is this done? I'd include more details on my code or messages, but I've been having trouble being rejected by the lister, so I'm being cautious. -- Dustin Oprea Software Engineer Intrepid Control Systems (1+) 248-726-0605 |
|
From: Damian P. <da...@gm...> - 2007-10-03 17:29:21
|
Can anybody help me with this problem. _____ From: FTDI Support [mailto:sup...@ft...] Sent: Wednesday, October 03, 2007 5:44 AM To: 'Damian Porter' Subject: RE: FT232BM Hello, The latest version of the driver we have is the one on the web. The original driver was written by a 3rd party and he offers his source code. http://ftdi-usb-sio.sourceforge.net/ Regards, Gordon Lunn Support Engineer FTDI Ltd 373 Scotland Street Glasgow Scotland UK G5 8QB Tel: +44 (0) 141 429 2777 Fax: +44 (0) 141 429 2758 Skype: ftdi.support2 Web: www.ftdichip.com From: Damian Porter [mailto:da...@gm...] Sent: 02 October 2007 19:38 To: Support1 Subject: RE: FT232BM Ok, just installed my USB hub and tested and the devices are still hanging, so the driver is definitely not working. Please advise me ASAP if there is a new driver available compared to the version online. Thanks. _____ From: FTDI Support [mailto:sup...@ft...] Sent: Thursday, September 27, 2007 10:11 AM To: 'Damian Porter' Subject: RE: FT232BM Hello, Probably, not a lot. You start getting into looking at data packets with USB analysers and signal integrity with scopes. All of which requires extra equipment. You might have access to a Windows PC to determine if the hardware works at all. Regards, Gordon Lunn Support Engineer FTDI Ltd 373 Scotland Street Glasgow Scotland UK G5 8QB Tel: +44 (0) 141 429 2777 Fax: +44 (0) 141 429 2758 Skype: ftdi.support2 Web: www.ftdichip.com From: Damian Porter [mailto:da...@gm...] Sent: 27 September 2007 14:36 To: Support1 Subject: RE: FT232BM I am going to buy a USB hub and see if that helps. If that does help want can you do to assist me. _____ From: FTDI Support [mailto:sup...@ft...] Sent: Thursday, September 27, 2007 9:30 AM To: 'Damian Porter' Subject: RE: FT232BM It would help because it would alter the USB termination. If the problem is with the USB termination (reasonable guess) then altering the termination may fix the problem. Regards, Gordon Lunn Support Engineer FTDI Ltd 373 Scotland Street Glasgow Scotland UK G5 8QB Tel: +44 (0) 141 429 2777 Fax: +44 (0) 141 429 2758 Skype: ftdi.support2 Web: www.ftdichip.com From: Damian Porter [mailto:da...@gm...] Sent: 27 September 2007 14:24 To: Support1 Subject: RE: FT232BM I plugged the devices in all available USB port and still the same thing, unfortunately I do not have a USB hub, but how would this hub help things. _____ From: FTDI Support [mailto:sup...@ft...] Sent: Thursday, September 27, 2007 9:10 AM To: 'Damian Porter' Subject: RE: FT232BM Hello, It does look like it could be a hardware issue with the device disconnecting and so having an invalid handle. You could perhaps try another USB port or connecting via a USB hub. Regards, Gordon Lunn Support Engineer FTDI Ltd 373 Scotland Street Glasgow Scotland UK G5 8QB Tel: +44 (0) 141 429 2777 Fax: +44 (0) 141 429 2758 Skype: ftdi.support2 Web: www.ftdichip.com From: Damian Porter [mailto:da...@gm...] Sent: 26 September 2007 14:27 To: Support1 Subject: FT232BM I have 2 4port serial usb devices pluged into my linux server runing centos 2.6.18. When i am connected and 2 or more console at the same time and hit the backspace key the console sessions hang. I there download you drivers and follow the instruction but after cmd "mount -a" i am stuck. Getting an error stating /proc/bus/usb busy. Even after removing (rmmod ftdi_sio and usbserial) the old module no sucess. Found this on kernel bugzilla site http://bugzilla.kernel.org/show_bug.cgi?id=5730. https://lists.linux-foundation.org/pipermail/bugme-new/2005-December/013478. html As you can see they are claming the problem is a hardware issue. Please let me know if there is a more uptodate driver. |
|
From: John H. <mis...@gm...> - 2007-10-02 00:16:35
|
This patch is still not included in the latest pre? On 9/5/07, Dan Smith <das...@ho...> wrote: > Hi Guys, > > I concur ... the patch worked for me using the latest kernel source. That > one case statement made all the difference. :) > > cheers, > > -dan > > >From: "John H." <mis...@gm...> > >To: "Oliver Neukum" <ol...@ne...> > >CC: lin...@li..., > >ftd...@li..., "das...@ho..." > ><das...@ho...>, "Bill Ryder" <bil...@gm...> > >Subject: Re: [linux-usb-devel] usb-uirt problems with ftdi_sio in 2.6.22.1 > >Date: Thu, 30 Aug 2007 15:37:54 -0500 > > > >Seems to work thus far! > > > >On 8/30/07, John H. <mis...@gm...> wrote: > > > I need the ftdi_sio.c and .h from that kernel. I will go download it > > > and report what happens. > > > > > > On 8/30/07, Oliver Neukum <ol...@ne...> wrote: > > > > Am Donnerstag 30 August 2007 schrieb John H.: > > > > > Can you tell me what kernel ftdi_sio.c to apply this to? > > > > > > > > I made it against 2.6.23-rc4 > > > > > > > > Regards > > > > Oliver > > > > > > > > > _________________________________________________________________ > Advertisement: It's simple! Sell your car for just $30 at CarPoint.com.au > http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%2Ecom%2Fcgi%2Dbin%2Fa%2Fci%5F450304%2Fet%5F2%2Fcg%5F801459%2Fpi%5F1004813%2Fai%5F859641&_t=762955845&_r=tig_SEP07&_m=EXT > > |
|
From: bill p. <bi...@be...> - 2007-09-27 21:08:41
|
On Thursday 27 Sep 2007 18:29, Craig Van Degrift wrote: > Bill, > > I am not sure I have the information you need, but I have written about > communication with a DLP-2232PB-G that uses a FT2232C chip. See if what I > have at > > http://yosemitefoothills.com/Electronics/FT2232C-based_projects.html > http://yosemitefoothills.com/Electronics/USBProgrammingSummary.html > http://yosemitefoothills.com/Electronics/FOSUG.html > > Might be helpful. Especially note how the O_ASYNC flag is set for the > read() function and the use of select(). > > Craig Van Degrift Thanks for the info - I'm not sure how relevant this is as I don't know how similar the various chips are. I have solved one problem - the reason why ftdi_sio wasn't being compiled when I tried to build the 6.22.8 kernel was that I had turned off the 'prompt for experimental drivers' flag. I didn't realise that the ftdi was classed as 'experimental'. I've just finished rebuilding the kernel, but it's time for bed so I'd better leave testing the new kernel until tomorrow! Bill -- +---------------------------------------+ | Bill Purvis, Amateur Mathematician | | email: bi...@be... | | http://bil.members.beeb.net | +---------------------------------------+ |
|
From: Craig V. D. <cr...@yo...> - 2007-09-27 17:32:40
|
Bill, I am not sure I have the information you need, but I have written about communication with a DLP-2232PB-G that uses a FT2232C chip. See if what I have at http://yosemitefoothills.com/Electronics/FT2232C-based_projects.html http://yosemitefoothills.com/Electronics/USBProgrammingSummary.html http://yosemitefoothills.com/Electronics/FOSUG.html Might be helpful. Especially note how the O_ASYNC flag is set for the read() function and the use of select(). Craig Van Degrift On Thursday 27 September 2007 05:40:53 bill purvis wrote: > Hi, > I'm not too well up on the workings of USB, so forgive my ignorance. > I've recently putchased a microcontroller which has an FT232R as > an interface chip. Plugging it into my system, using the 2.6.8.1 kernel > activates the /dev/ttyUSB00 port and I can open it OK using minicom. > I get no response from the controller, though. The controller works > fine on a Windows box using a proprietary terminal emulator provided > with the device. I have tried downloading the ftdi_sio module source > from the FTDI web site but it won't compile with my kernel sources. > I next tried downloading the latest kernel sources from www.kernel.org > and tried configuring and compiling that. Despite a full search through > the config options I can't find anything to turn on compilation > of ftdi_sio.c - the source is there, the requisite #define is missing > from .config. > Anyone have any suggestions as to where I go next? > > Bill |
|
From: bill p. <bi...@be...> - 2007-09-27 12:41:03
|
Hi, I'm not too well up on the workings of USB, so forgive my ignorance. I've recently putchased a microcontroller which has an FT232R as an interface chip. Plugging it into my system, using the 2.6.8.1 kernel activates the /dev/ttyUSB00 port and I can open it OK using minicom. I get no response from the controller, though. The controller works fine on a Windows box using a proprietary terminal emulator provided with the device. I have tried downloading the ftdi_sio module source from the FTDI web site but it won't compile with my kernel sources. I next tried downloading the latest kernel sources from www.kernel.org and tried configuring and compiling that. Despite a full search through the config options I can't find anything to turn on compilation of ftdi_sio.c - the source is there, the requisite #define is missing from .config. Anyone have any suggestions as to where I go next? Bill -- +---------------------------------------+ | Bill Purvis, Amateur Mathematician | | email: bi...@be... | | http://bil.members.beeb.net | +---------------------------------------+ |
|
From: [Carlos H.] <ca...@gm...> - 2007-09-24 14:55:39
|
Hello all,
We've recently switched to the following FTDI chip:
Bus 5 Device 3: ID 0403:6001 Future Technology Devices International, Ltd
8-bit FIFO
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 8-bit FIFO
bcdDevice 6.00
iManufacturer 1 FTDI
iProduct 2 FT232R USB UART
iSerial 3 A2001DYM
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 FT232R USB UART
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
I have legacy software which makes use of the FIONREAD (0x54b1) ioctl to see
how many bytes are available on the FIFO, but by using the ftdi_sio module
on kernel 2.6.19 I'm getting the following error (took from debug output).
Sep 24 11:05:44 carlos kernel: drivers/usb/serial/ftdi_sio.c: ftdi_ioctl cmd
0x541b
Sep 24 11:05:44 carlos kernel: drivers/usb/serial/ftdi_sio.c: ftdi_ioctl arg
not supported - it was 0x541b - check /usr/include/asm/ioctls.h
Is this really not implemented? Could it be done easily? Thanks in advance
for any hints.
--
[]'s
Carlos H.
|
|
From: John H. <mis...@gm...> - 2007-08-30 20:37:50
|
Seems to work thus far! On 8/30/07, John H. <mis...@gm...> wrote: > I need the ftdi_sio.c and .h from that kernel. I will go download it > and report what happens. > > On 8/30/07, Oliver Neukum <ol...@ne...> wrote: > > Am Donnerstag 30 August 2007 schrieb John H.: > > > Can you tell me what kernel ftdi_sio.c to apply this to? > > > > I made it against 2.6.23-rc4 > > > > Regards > > Oliver > > > |
|
From: John H. <mis...@gm...> - 2007-08-30 20:08:07
|
I need the ftdi_sio.c and .h from that kernel. I will go download it and report what happens. On 8/30/07, Oliver Neukum <ol...@ne...> wrote: > Am Donnerstag 30 August 2007 schrieb John H.: > > Can you tell me what kernel ftdi_sio.c to apply this to? > > I made it against 2.6.23-rc4 > > Regards > Oliver > |
|
From: John H. <mis...@gm...> - 2007-08-30 19:35:42
|
Can you tell me what kernel ftdi_sio.c to apply this to? On 8/30/07, Oliver Neukum <ol...@ne...> wrote: > Am Freitag 24 August 2007 schrieb John H.: > > I dunno, I've only been using usb-uirt. The bugzilla entry has the > > latest problem described. > > Did you try the additional suggested patch? > I am attaching it for your convinience. > > Regards > Oliver > > |
|
From: John H. <mis...@gm...> - 2007-08-24 16:01:57
|
I dunno, I've only been using usb-uirt. The bugzilla entry has the latest problem described. On 8/24/07, Oliver Neukum <ol...@ne...> wrote: > Am Freitag 24 August 2007 schrieb John H.: > > Oliver, your patch never actually fixed the previous error, which is > > why I went back to an older source at the time. > > > > Now this seems to be a different error, I dunno, I just know it > > results in the usb-uirt not working still. > > Yet, I got reports about it working. This is odd. Are there > different devices involved? > > Regards > Oliver > |
|
From: John H. <mis...@gm...> - 2007-08-24 13:23:55
|
Oliver, your patch never actually fixed the previous error, which is why I went back to an older source at the time. Now this seems to be a different error, I dunno, I just know it results in the usb-uirt not working still. On 8/24/07, Oliver Neukum <ol...@ne...> wrote: > Am Freitag 24 August 2007 schrieb John H.: > > Bill, thanks. > > > > Unfortunately, I got no response from the linux-usb-developers list. > > The bugzilla is still outstanding. It's rather ridiculous that the bug > > would go unfixed that long, particularly when it USED to work! In > > other words, someone broke it when they changed stuff and they are not > > fixing it as of now. > > The problem was reported and I made a patch some time ago. Then > another error seems to have cropped up. > Could somebody make a clear report to the list, about what exactly > are the symptoms without the patch and what happens after the patch > and why it is insufficient? > > Regards > Oliver > > |
|
From: John H. <mis...@gm...> - 2007-08-24 05:23:21
|
Greg, here's the bugzilla entry that answers all your questions. The end is the most relevant. http://bugzilla.kernel.org/show_bug.cgi?id=8564 I am currently using it without incident on 2.6.22.1 with the ftdi_sio.h and .c from the earlier kernel described in that bugzilla entry. On 8/23/07, Greg KH <gr...@kr...> wrote: > On Thu, Aug 23, 2007 at 08:13:40PM -0500, John H. wrote: > > Bill, thanks. > > > > Unfortunately, I got no response from the linux-usb-developers list. > > Hm, did I miss your message somehow? What was the Subject: ? > > > The bugzilla is still outstanding. It's rather ridiculous that the bug > > would go unfixed that long, particularly when it USED to work! In > > other words, someone broke it when they changed stuff and they are not > > fixing it as of now. > > Are you sure it used to work? > > And what is the problem with that ioctl not working now? > > Anyway, more details are appreciated. > > thanks, > > greg k-h > |
|
From: John H. <mis...@gm...> - 2007-08-24 01:13:38
|
Bill, thanks. Unfortunately, I got no response from the linux-usb-developers list. The bugzilla is still outstanding. It's rather ridiculous that the bug would go unfixed that long, particularly when it USED to work! In other words, someone broke it when they changed stuff and they are not fixing it as of now. On 8/23/07, Bill Ryder <bil...@gm...> wrote: > Hi John, > > I have had a good look at the driver and I finally understand the problem. > However I can't fix or test it because I would need your device. It has to > do with quirk handling which none of the really old devices I have need. > > So unfortunately you are on your own! You need to find a developer who has > one of your devices. > > You should however try the linux usb developers list. That is where people > have been submitting these patches I suspect. Someone there must have had a > device the same as yours. > > I think you'll be lucky if you can get someone to work on an old kernel > though. > > If you pay for redhat support you should be able to get them to look at it > though. > > > > On 8/24/07, John H. <mis...@gm...> wrote: > > Sorry, dan, no one seems interested in fixing it despite this bug > > being in several kernel versions. > > > > The only solution is to use the source from an older kernel, the > > ftdi_sio.h and ftdi_sio.c. > > > > You can see from the bugzilla entry what to do... > > > > http://bugzilla.kernel.org/show_bug.cgi?id=8564 > > > > On 8/23/07, das...@ho... < das...@ho...> wrote: > > > Hi John, > > > > > > Did you find a solution/patch for the issue below? I have exactly the > same problem with my new uirt, and I can't find any references to it apart > from yours. I've tried the latest CVS, packaged version for my distro > (arch), 0.8.2 source from the lirc.org site ... sweet fanny albright with > all three. > > > > > > kind regards, > > > > > > -dan > > > > > > John H.-2 wrote: > > > > > > > > This was broken a while back with fedora 7's kernel, and someone told > > > > me a patch I could try, but now it is broken again in > > > > Linux home 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 > > > > i686 i386 GNU/Linux > > > > > > > > What to do? Can I at least patch or do something to where it works > > > > again for now? > > > > > > > >> > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > > >> > lircd: tty_setdtr: Bad address > > > >> This is a problem of the ftdi_sio driver. > > > >> ftdi_tiocmget is obviously not implemented for your hardware. > > > >> You should report this to the driver authors. > > > >> > > > >> Christoph > > > > > > > > -- > > > > ./lircd -H usb_uirt_raw -d /dev/ttyUSB0 -n -D1 > > > > lircd: started server socket > > > > lircd: parsing remote > > > > lircd: parsing DISH_1 remote > > > > lircd: parsing remote > > > > lircd: parsing PinnacleSysRemote remote > > > > lircd: config file read > > > > lircd: lircd(usb_uirt_raw) ready > > > > lircd: registering local client > > > > lircd: accepted new client on /dev/lircd > > > > lircd: writing command 23 > > > > lircd: 23 dd > > > > lircd: wrote 2 > > > > lircd: cmd res 3: > > > > lircd: 09 05 01 > > > > lircd: > > > > lircd: uirt2_raw: checksum error > > > > lircd: uirt2: detection of uirt2 failed > > > > lircd: uirt2: trying to detect newer uirt firmware > > > > lircd: writing command 23 > > > > lircd: 23 dd > > > > lircd: wrote 2 > > > > lircd: cmd res 8: > > > > lircd: 09 05 01 01 1a 03 04 cf > > > > lircd: > > > > lircd: uirt2_raw: UIRT version 0905 ok > > > > lircd: writing command 21 > > > > lircd: 21 df > > > > lircd: wrote 2 > > > > lircd: cmd res 1: > > > > lircd: 21 > > > > lircd: > > > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > > > lircd: tty_setdtr: Bad address > > > > lircd: uirt2_raw: could not set DTR > > > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > > > lircd: tty_setdtr: Bad address > > > > lircd: caught signal > > > > Terminated > > > > > > > > On 12 Aug 2007 09:40:00 +0200, Christoph Bartelmus <li...@ba...> > > > > wrote: > > > >> Hi John, > > > >> > > > >> on 12 Aug 07 at 02:22, you wrote: > > > >> [...] > > > >> > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > > >> > lircd: tty_setdtr: Bad address > > > >> > > > >> This is a problem of the ftdi_sio driver. > > > >> ftdi_tiocmget is obviously not implemented for your hardware. > > > >> You should report this to the driver authors. > > > >> > > > >> Christoph > > > >> > > > >> > ------------------------------------------------------------------------- > > > >> This SF.net email is sponsored by: Splunk Inc. > > > >> Still grepping through log files to find problems? Stop. > > > >> Now Search log events and configuration files using AJAX and a > browser. > > > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > >> > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Splunk Inc. > > > > Still grepping through log files to find problems? Stop. > > > > Now Search log events and configuration files using AJAX and a > browser. > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > > > > > > > Quoted from: > > > > http://www.nabble.com/usb-uirt-problems-with-ftdi_sio-in-2.6.22.1-tf4255931.html#a12112175 > > > > > > > > > > |
|
From: Bill R. <bil...@gm...> - 2007-08-23 23:50:58
|
Hi John, I have had a good look at the driver and I finally understand the problem. However I can't fix or test it because I would need your device. It has to do with quirk handling which none of the really old devices I have need. So unfortunately you are on your own! You need to find a developer who has one of your devices. You should however try the linux usb developers list. That is where people have been submitting these patches I suspect. Someone there must have had a device the same as yours. I think you'll be lucky if you can get someone to work on an old kernel though. If you pay for redhat support you should be able to get them to look at it though. On 8/24/07, John H. <mis...@gm...> wrote: > > Sorry, dan, no one seems interested in fixing it despite this bug > being in several kernel versions. > > The only solution is to use the source from an older kernel, the > ftdi_sio.h and ftdi_sio.c. > > You can see from the bugzilla entry what to do... > > http://bugzilla.kernel.org/show_bug.cgi?id=8564 > > On 8/23/07, das...@ho... <das...@ho...> wrote: > > Hi John, > > > > Did you find a solution/patch for the issue below? I have exactly the > same problem with my new uirt, and I can't find any references to it apart > from yours. I've tried the latest CVS, packaged version for my distro > (arch), 0.8.2 source from the lirc.org site ... sweet fanny albright with > all three. > > > > kind regards, > > > > -dan > > > > John H.-2 wrote: > > > > > > This was broken a while back with fedora 7's kernel, and someone told > > > me a patch I could try, but now it is broken again in > > > Linux home 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 > > > i686 i386 GNU/Linux > > > > > > What to do? Can I at least patch or do something to where it works > > > again for now? > > > > > >> > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > >> > lircd: tty_setdtr: Bad address > > >> This is a problem of the ftdi_sio driver. > > >> ftdi_tiocmget is obviously not implemented for your hardware. > > >> You should report this to the driver authors. > > >> > > >> Christoph > > > > > > -- > > > ./lircd -H usb_uirt_raw -d /dev/ttyUSB0 -n -D1 > > > lircd: started server socket > > > lircd: parsing remote > > > lircd: parsing DISH_1 remote > > > lircd: parsing remote > > > lircd: parsing PinnacleSysRemote remote > > > lircd: config file read > > > lircd: lircd(usb_uirt_raw) ready > > > lircd: registering local client > > > lircd: accepted new client on /dev/lircd > > > lircd: writing command 23 > > > lircd: 23 dd > > > lircd: wrote 2 > > > lircd: cmd res 3: > > > lircd: 09 05 01 > > > lircd: > > > lircd: uirt2_raw: checksum error > > > lircd: uirt2: detection of uirt2 failed > > > lircd: uirt2: trying to detect newer uirt firmware > > > lircd: writing command 23 > > > lircd: 23 dd > > > lircd: wrote 2 > > > lircd: cmd res 8: > > > lircd: 09 05 01 01 1a 03 04 cf > > > lircd: > > > lircd: uirt2_raw: UIRT version 0905 ok > > > lircd: writing command 21 > > > lircd: 21 df > > > lircd: wrote 2 > > > lircd: cmd res 1: > > > lircd: 21 > > > lircd: > > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > > lircd: tty_setdtr: Bad address > > > lircd: uirt2_raw: could not set DTR > > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > > lircd: tty_setdtr: Bad address > > > lircd: caught signal > > > Terminated > > > > > > On 12 Aug 2007 09:40:00 +0200, Christoph Bartelmus <li...@ba...> > > > wrote: > > >> Hi John, > > >> > > >> on 12 Aug 07 at 02:22, you wrote: > > >> [...] > > >> > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > >> > lircd: tty_setdtr: Bad address > > >> > > >> This is a problem of the ftdi_sio driver. > > >> ftdi_tiocmget is obviously not implemented for your hardware. > > >> You should report this to the driver authors. > > >> > > >> Christoph > > >> > > >> > ------------------------------------------------------------------------- > > >> This SF.net email is sponsored by: Splunk Inc. > > >> Still grepping through log files to find problems? Stop. > > >> Now Search log events and configuration files using AJAX and a > browser. > > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > > >> > > > > > > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a > browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > > > > Quoted from: > > > http://www.nabble.com/usb-uirt-problems-with-ftdi_sio-in-2.6.22.1-tf4255931.html#a12112175 > > > > > |
|
From: John H. <mis...@gm...> - 2007-08-23 18:13:25
|
Sorry, dan, no one seems interested in fixing it despite this bug being in several kernel versions. The only solution is to use the source from an older kernel, the ftdi_sio.h and ftdi_sio.c. You can see from the bugzilla entry what to do... http://bugzilla.kernel.org/show_bug.cgi?id=8564 On 8/23/07, das...@ho... <das...@ho...> wrote: > Hi John, > > Did you find a solution/patch for the issue below? I have exactly the same problem with my new uirt, and I can't find any references to it apart from yours. I've tried the latest CVS, packaged version for my distro (arch), 0.8.2 source from the lirc.org site ... sweet fanny albright with all three. > > kind regards, > > -dan > > John H.-2 wrote: > > > > This was broken a while back with fedora 7's kernel, and someone told > > me a patch I could try, but now it is broken again in > > Linux home 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 > > i686 i386 GNU/Linux > > > > What to do? Can I at least patch or do something to where it works > > again for now? > > > >> > lircd: tty_setdtr: ioctl(TIOCMGET) failed > >> > lircd: tty_setdtr: Bad address > >> This is a problem of the ftdi_sio driver. > >> ftdi_tiocmget is obviously not implemented for your hardware. > >> You should report this to the driver authors. > >> > >> Christoph > > > > -- > > ./lircd -H usb_uirt_raw -d /dev/ttyUSB0 -n -D1 > > lircd: started server socket > > lircd: parsing remote > > lircd: parsing DISH_1 remote > > lircd: parsing remote > > lircd: parsing PinnacleSysRemote remote > > lircd: config file read > > lircd: lircd(usb_uirt_raw) ready > > lircd: registering local client > > lircd: accepted new client on /dev/lircd > > lircd: writing command 23 > > lircd: 23 dd > > lircd: wrote 2 > > lircd: cmd res 3: > > lircd: 09 05 01 > > lircd: > > lircd: uirt2_raw: checksum error > > lircd: uirt2: detection of uirt2 failed > > lircd: uirt2: trying to detect newer uirt firmware > > lircd: writing command 23 > > lircd: 23 dd > > lircd: wrote 2 > > lircd: cmd res 8: > > lircd: 09 05 01 01 1a 03 04 cf > > lircd: > > lircd: uirt2_raw: UIRT version 0905 ok > > lircd: writing command 21 > > lircd: 21 df > > lircd: wrote 2 > > lircd: cmd res 1: > > lircd: 21 > > lircd: > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > lircd: tty_setdtr: Bad address > > lircd: uirt2_raw: could not set DTR > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > lircd: tty_setdtr: Bad address > > lircd: caught signal > > Terminated > > > > On 12 Aug 2007 09:40:00 +0200, Christoph Bartelmus <li...@ba...> > > wrote: > >> Hi John, > >> > >> on 12 Aug 07 at 02:22, you wrote: > >> [...] > >> > lircd: tty_setdtr: ioctl(TIOCMGET) failed > >> > lircd: tty_setdtr: Bad address > >> > >> This is a problem of the ftdi_sio driver. > >> ftdi_tiocmget is obviously not implemented for your hardware. > >> You should report this to the driver authors. > >> > >> Christoph > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. > >> Still grepping through log files to find problems? Stop. > >> Now Search log events and configuration files using AJAX and a browser. > >> Download your FREE copy of Splunk now >> http://get.splunk.com/ > >> > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > > Quoted from: > http://www.nabble.com/usb-uirt-problems-with-ftdi_sio-in-2.6.22.1-tf4255931.html#a12112175 > > |
|
From: John H. <mis...@gm...> - 2007-08-17 04:23:46
|
So I again did what I specified in the bug report http://bugzilla.kernel.org/show_bug.cgi?id=8564 Used the ftdi_sio.h and ftdi_sio.c from http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.20.y.git;a=tree;f=drivers/usb/serial;h=535edb4ac2d4c6b03bd3ca641c44aae8013b4dd9;hb=fcfbb42bd476ed54b598d917d3b9b63d8835093e With kernel uname -a Linux home 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 i686 i386 GNU/Linux And it works with 2.6.22.1-41. Apparently sometime after that kernel the driver has been broken for usb-uirt, pretty much ever since. On 8/16/07, John H. <mis...@gm...> wrote: > The current kernel one doesn't work:) > > Did you get that bugzilla forward? That outlines the whole fix that I > tried a while back. > > On 8/16/07, Bill Ryder <bil...@gm...> wrote: > > > > > > On 8/16/07, John H. <mis...@gm...> wrote: > > > I can't remember, I will try to look at the old email. > > > > > > Can I do that debug stuff from the current kernel, or you need me to > > > do it with the new one that doesn't work with usb-uirt? > > > > It should work with both. > > > > I need to see the one that doesn't work. > > > > Also can you send me a diff between the ftdi_sio.c that works and the one > > that doesn't? > > > > > > > > > On 8/16/07, Bill Ryder <bil...@gm...> wrote: > > > > > > > > > > > > On 8/16/07, John H. <mis...@gm...> wrote: > > > > > Oh, i had to patch the driver for that kernel. I am using that kernel > > > > > again because with my upgrade to fedora 7 and the first kernel it had, > > > > > ftdi_sio stopped working right with usb-uirt. I had to patch the > > > > > kernel I am currently using to work at all with it. > > > > > > > > What did you do exactly? > > > > > > > > And to debug do this: > > > > > > > > echo 'Y' > /sys/module/ftdi_sio/parameters/debug > > > > > > > > The output will end up in dmesg I think (or one of the logs in /var/log) > > > > > > > > > > > > > > > > > > > > > > > > |
350 messages has been excluded from this view by a project administrator.
