28 Jun, 2011

1 commit

  • appended patch adds support for the new FTDI FT232H chip. This chip is a
    single channel version of the dual FT2232H/quad FT4232H, coming with it's
    own default PID 0x6014 (FT2232H uses the same PID 0x6010 like FT2232C,
    FT4232H has also it's own PID).

    The patch was checked on an UM232H module and a terminal program with TX/RX
    shorted to that typing in the terminal reproduced the characters.

    Signed-off-by: Uwe Bonnes
    Cc: stable
    Signed-off-by: Greg Kroah-Hartman

    Uwe Bonnes
     

21 May, 2010

1 commit


03 Mar, 2010

1 commit


24 Dec, 2009

1 commit

  • This is a strictly move-only patch to relocate all FTDI device
    product ID definitions to their own ftdi_sio_ids.h header
    (following the usual *_ids.h kernel tree convention, too),
    thus correcting the slightly too messy appearance
    (crucial driver defines were stuck somewhere in the decaying middle swamp
    of the huge existing header).

    Compile-tested, based on latest mainline git.

    Signed-off-by: Andreas Mohr
    Signed-off-by: Greg Kroah-Hartman

    Andreas Mohr
     

12 Dec, 2009

1 commit


23 Sep, 2009

3 commits


08 Aug, 2009

2 commits


29 Jul, 2009

1 commit


13 Jul, 2009

4 commits

  • Adds USB ID for Turtelizer, an FT2232L-based JTAG/RS-232 adapter.

    Signed-off-by: Krzysztof Ha³asa
    Signed-off-by: Greg Kroah-Hartman

    Krzysztof Halasa
     
  • It enhances the driver for FTDI-based USB serial adapters to recognize and
    support Northern Digital Inc (NDI) measurement equipment. NDI has been
    providing this patch for various kernel flavors for several years and we would
    like to see these changes built in to the driver so that our equipement works
    without the need for customers to patch the kernel themselves.

    The patch makes small modifications to 2 files: ./drivers/usb/serial/ftdi_sio.c
    and ./drivers/usb/serial/ftdi_sio.h. It accomplishes 3 things:

    1. Define the VID and PIDs to allow the driver to recognize the NDI devices.
    2. Map the 19200 baud rate setting to our higher baud rate of 1.2Mb
    We would have chosen to map 38400 to the higher rate, similar to what
    several other vendors have done, but some of our legacy customers actually
    use 38400, therefore we remap 19200 to the higher rate.
    3. We set the default transmit latency in the FTDI chip to 1ms for our devices.
    Our devices are typically polled at 60Hz and the default ftdi latency
    seriously affects turn-around time and results in missed data frames. We
    have created a modprobe option that allows this setting to be increased.
    This has proven necessary particularly in some virtualized environments.

    Signed-off-by: Martin P. Geleynse
    Signed-off-by: Greg Kroah-Hartman

    Martin Geleynse
     
  • It seems an USB device with vendor id 0403 and product code FB80 has an
    FTDI serial io chip as well: http://ftdichip.com/Drivers/D2XX.htm
    This device in fact is a true random generantor by comsci:
    http://comscire.com/Products/R2000KU/
    So the following patch should add support for this device if I am
    correct. Not tested as I do not own this device (I would like support in
    the kernel so that my entropybroker application (which distributes
    entrop data (random values) between servers and clients)).

    From: Folkert van Heusden
    Signed-off-by: Greg Kroah-Hartman

    Folkert van Heusden
     
  • The product ID's for the following devices have been added:
    - LOAD-n-GO
    - ICD-U64
    - PRIME-8

    Signed-off-by: Jan Capek
    Signed-off-by: Greg Kroah-Hartman

    Jan Capek
     

16 Jun, 2009

2 commits

  • Added support for FTDI's USB 2.0 hi-speed devices - FT2232H (2
    interfaces) and FT4232H (4 interfaces), including a new baud rate
    calculation for these devices which can now achieve up to 12Mbaud by
    turning off a divide by 2.5 in the baud rate generator of the chips. In
    order to achieve baud rates of
    Signed-off-by: Greg Kroah-Hartman

    Mark Adamson
     
  • I would like to have added new device to usbserial/ftdi_sio driver.
    These ids used USB track device (http://www.l-and-b.dk/access_alt.html).
    They use differend device IDs, but it works as standard usb-serial
    conventer.

    From: Daniel Suchy
    Signed-off-by: Greg Kroah-Hartman

    Daniel Suchy
     

09 May, 2009

1 commit


18 Apr, 2009

1 commit


18 Mar, 2009

2 commits


10 Feb, 2009

1 commit


28 Jan, 2009

2 commits


18 Dec, 2008

2 commits

  • The following patch adds in the USB PID for Ewert Energy System's CANdapter
    device (CANBUS to USB-Serial which uses the FTDI 245R chipset) to the ftdi_sio
    device driver.

    The patch was tested successfully on Linux kernel 2.6.27 under Ubuntu.

    Relevant output from /proc/bus/usb/devices (With patch installed):

    T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
    D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
    P: Vendor=0403 ProdID=9f80 Rev= 6.00
    S: Manufacturer=Ewert Energy Systems
    S: Product=CANdapter
    S: SerialNumber=A6RGB3Z3
    C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 90mA
    I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=ftdi_sio
    E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

    Signed-off-by: Andrew Ewert
    Signed-off-by: Greg Kroah-Hartman

    Andrew Ewert
     
  • Someone on rmweb reminded me this had been overlooked from ages ago..

    Add the identifiers for the Sprog II USB. This is a DCC control interface
    using the FTDI-SIO hardware: http://www.sprog-dcc.co.uk/. People have been
    using it with insmod options for ages, this just puts it into the driver
    data.

    Signed-off-by: Alan Cox
    Signed-off-by: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Alan Cox
     

18 Oct, 2008

1 commit

  • Add Oceanic PID to ftdi_sio driver

    Oceanic dive computers (such as the VT3 --
    http://www.oceanicworldwide.com/p_computers_vt3.html) all use an onboard
    FTDI serial converter, with the FTDI vid and a PID of 0xf460. The
    attached patch adds that pid to ftdi_sio; driver connects to my VT3
    after that.

    Signed-off-by: Vladimir Vukicevic
    Signed-off-by: Greg Kroah-Hartman

    Vladimir Vukicevic
     

24 Sep, 2008

2 commits


14 Aug, 2008

3 commits


23 Jul, 2008

1 commit


04 Jul, 2008

1 commit

  • Here's a new device ID for the ftdio_sio driver.
    The diff is with linus's tree as of this morning.

    The device is the RigExpert Tiny USB Soundcard Transceiver Interface for ham
    radio.

    (I didn't actually test this. A fellow ham couldn't get the device to work, and
    I suggested binding the device ID using sysfs - see
    "http://jk.ufisa.uninett.no/usb/". However, he had had moved on to other things
    by then. I guess adding the device ID to the kernel "on spec" won't hurt.
    The relevant part of cat /proc/bus/usb/devices shows:

    T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
    D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
    P: Vendor=0403 ProdID=ed22 Rev= 5.00
    S: Manufacturer=FTDI
    S: Product=MixW RigExpert Tiny
    S: SerialNumber=00000000
    C:* #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=100mA
    I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    I:* If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
    E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    E: Ad=04(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
    )

    From: Jon K Hellan
    Signed-off-by: Greg Kroah-Hartman

    Jon K Hellan
     

30 May, 2008

1 commit

  • This patch adds support for the range of PIDs
    that have been allocated for FTDI based devices
    at Matrix Orbital.

    A small number of units have been shipped early 2008
    with a faulty USB Descriptor. Products that may have
    this issue have been marked with the existing quirk to
    work around the problem.

    Signed-off-by: R. Molenkamp
    Signed-off-by: Greg Kroah-Hartman

    Ray Molenkamp
     

21 May, 2008

1 commit


03 May, 2008

1 commit


11 Mar, 2008

1 commit

  • Here is a patch that adds support for the propox jtagcable II dongle
    (http://www.propox.com/products/t_117.html): their PID was missing,
    therefore we were not able to have the device recognized though it uses
    a standard FTDI chip.

    Signed-off-by: Mirko Bordignon
    Signed-off-by: Greg Kroah-Hartman

    Mirko Bordignon
     

05 Mar, 2008

1 commit


02 Feb, 2008

1 commit

  • [PATCH] ftdi_sio: add support for more FTDI based JTAG adaptors

    There are more devices similar to the Olimex JTAG adaptor, in that the first
    port of the FT2232C is used for JTAG, and only the second port is available as
    UART.

    I have thus renamed ftdi_olimex_{probe,quirk} to ftdi_jtag_{probe,quirk} and
    added vendor/product ID's for the OpenMoko Neo1973 Debug Board as well as the
    OOCDlink device.

    I've also updated the KERN_INFO message sent to userspace to remove the word
    'olimex' and an extra '\n' that was causing an empty line in dmesg.

    Signed-off-by: Harald Welte
    Signed-off-by: Greg Kroah-Hartman

    Harald Welte