Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

getting the latest FTDI usb-to-serial converter driver to work on 2.6.27

18 views
Skip to first unread message

Rage

unread,
Jul 30, 2009, 11:38:42 AM7/30/09
to
I'm having trouble compiling the latest(http://www.ftdichip.com/
Drivers/VCP.htm) ftdi usb to serial converter drivers for 2.6.27.

The problem is I think that something seems to have changed in 2.6
kernel
1) members: ´num_interrupt_in`, ´num_bulk_in`, ´num_bulk_out` are
missing from ´struct usb_serial_driver`:
2) member ´open_count` is missing from ´struct usb_serial_port`

The location of member ´tty` in ´struct usb_serial_port` was changed,
but that i could fix
( modified source code: http://pastebin.com/m2961e9c7 )

These are the last compiler errors, which i don't know how to fix:

drivers/usb/serial/ftdi_sio.c:658: error: unknown field
`num_interrupt_in' specified in initializer
drivers/usb/serial/ftdi_sio.c:659: error: unknown field `num_bulk_in'
specified in initializer
drivers/usb/serial/ftdi_sio.c:659: warning: missing braces around
initializer
drivers/usb/serial/ftdi_sio.c:659: warning: (near initialization for
`ftdi_sio_device.driver_list')
drivers/usb/serial/ftdi_sio.c:659: warning: initialization makes
pointer from integer without a cast
drivers/usb/serial/ftdi_sio.c:660: error: unknown field `num_bulk_out'
specified in initializer
drivers/usb/serial/ftdi_sio.c:660: warning: initialization makes
pointer from integer without a cast
drivers/usb/serial/ftdi_sio.c:666: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:667: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:668: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:669: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:670: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:671: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:672: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:675: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:676: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:677: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:678: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c:679: warning: initialization from
incompatible pointer type
drivers/usb/serial/ftdi_sio.c: In function `ftdi_read_bulk_callback':
drivers/usb/serial/ftdi_sio.c:1770: error: structure has no member
named `open_count'
drivers/usb/serial/ftdi_sio.c: In function `ftdi_process_read':
drivers/usb/serial/ftdi_sio.c:1826: error: structure has no member
named `open_count'
drivers/usb/serial/ftdi_sio.c:1977: error: structure has no member
named `open_count'
drivers/usb/serial/ftdi_sio.c:1990: error: structure has no member
named `open_count'


Thanks to anyone who can guide me in the right direction,

Roland

Rage

unread,
Aug 4, 2009, 12:58:38 PM8/4/09
to
So here's how to make the drivers compile and send/receive data
through the ports(haven't got the change to thoroughly test it), for
anyone who might be interested:

Got this from ftdichip.com support


Hello,

Yes Linux changed some of the files the driver refers to.

These patches should allow you to compile

http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-serial-ftdi-add-high-speed-device-support.patch
or
ftp://ftp.ua.kernel.org/pub/mirrors/kernel.org/linux/kernel/people/gregkh/usb/2.6/2.6.30/usb-serial-ftdi-add-high-speed-device-support.patch

http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-ftdi_sio-fix-hi-speed-device-packet-size-calculation.patch
or
http://ring.nict.go.jp/archives/linux/kernel.org/kernel/people/gregkh/usb/2.6/2.6.30/usb-ftdi_sio-fix-hi-speed-device-packet-size-calculation.patch


Apparently it will all be working again by kernel 2.6.31

Regards,

Gordon Lunn

Senior Applications Engineer


PS: failed hunks (2lines of code) should be changed manually with a
text editor

0 new messages