From: "Benedek László" <benedekl@gmail.com>
To: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: New FTDI serial io vendor/product id patch
Date: Fri, 01 Apr 2011 21:46:25 +0200 [thread overview]
Message-ID: <4D962B91.5090702@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
Dear list,
I have an USB Atmel programmer which uses the FTDI driver. It has a
VID/PID pair of 0403:FA33. It identifies itself as "TavIR STK500". Here
is a photo of the the device:
http://avr.tavir.hu/images/contents/809/809l-stk500-m.jpg
lsusb output:
Bus 002 Device 005: ID 0403:fa33 Future Technology Devices
International, Ltd
dmesg output with patched kernel:
[ 1835.915073] usb 2-1.3: new full speed USB device using ehci_hcd and
address 5
[ 1836.012322] usb 2-1.3: New USB device found, idVendor=0403,
idProduct=fa33
[ 1836.012329] usb 2-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 1836.012336] usb 2-1.3: Product: TavIR STK500
[ 1836.012340] usb 2-1.3: Manufacturer: TavIR AVR
[ 1836.014620] ftdi_sio 2-1.3:1.0: FTDI USB Serial Device converter detected
[ 1836.014723] usb 2-1.3: Detected FT232RL
[ 1836.014730] usb 2-1.3: Number of endpoints 2
[ 1836.014737] usb 2-1.3: Endpoint 1 MaxPacketSize 64
[ 1836.014743] usb 2-1.3: Endpoint 2 MaxPacketSize 64
[ 1836.014749] usb 2-1.3: Setting MaxPacketSize 64
[ 1836.015394] usb 2-1.3: FTDI USB Serial Device converter now attached
to ttyUSB1
Please consider applying this trivial patch which allows the system to
recognise the device as a serial io port.
I'm not a subscriber of this mailing list, so please CC the answers
personally too. Thank you.
Regards,
Benedek László
[-- Attachment #2: 0001-USB-serial-FTDI-with-product-code-FA33-and-vendor-id.patch --]
[-- Type: text/x-diff, Size: 1477 bytes --]
>From 8f1c09d60e70f793bf818380a0c7d2a5064088e3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Benedek=20L=C3=A1szl=C3=B3?= <benedekl@gmail.com>
Date: Fri, 1 Apr 2011 19:48:14 +0200
Subject: [PATCH] USB: serial: FTDI with product code FA33 and vendor id 0403
The TavIR-AVR USB STK500 Atmel programmer (0403:FA33) uses the
FTDI serial io driver, so add support for this device.
---
drivers/usb/serial/ftdi_sio.c | 1 +
drivers/usb/serial/ftdi_sio_ids.h | 5 +++++
2 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/serial/ftdi_sio.c b/drivers/usb/serial/ftdi_sio.c
index f349a36..f1b047a 100644
--- a/drivers/usb/serial/ftdi_sio.c
+++ b/drivers/usb/serial/ftdi_sio.c
@@ -563,6 +563,7 @@ static struct usb_device_id id_table_combined [] = {
{ USB_DEVICE(FTDI_VID, FTDI_IBS_APP70_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_IBS_PEDO_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_IBS_PROD_PID) },
+ { USB_DEVICE(FTDI_VID, FTDI_TAVIR_STK500_PID) },
/*
* ELV devices:
*/
diff --git a/drivers/usb/serial/ftdi_sio_ids.h b/drivers/usb/serial/ftdi_sio_ids.h
index 117e8e6..ce6ed76 100644
--- a/drivers/usb/serial/ftdi_sio_ids.h
+++ b/drivers/usb/serial/ftdi_sio_ids.h
@@ -489,6 +489,11 @@
/* www.canusb.com Lawicel CANUSB device (FTDI_VID) */
#define FTDI_CANUSB_PID 0xFFA8 /* Product Id */
+/*
+ * TavIR AVR product ids (FTDI_VID)
+ */
+#define FTDI_TAVIR_STK500_PID 0xFA33 /* STK500 AVR programmer */
+
/********************************/
--
1.7.4.1
reply other threads:[~2011-04-01 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D962B91.5090702@gmail.com \
--to=benedekl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.