From: Johan Hovold <jhovold@gmail.com>
To: Jean-Francois Argentino <jf.argentino@osean.fr>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] ftdi_sio: adding support for OLIMEX ARM-USB-OCD-H
Date: Wed, 9 Mar 2011 22:13:20 +0100 [thread overview]
Message-ID: <20110309211320.GB14009@localhost> (raw)
In-Reply-To: <4D6BC4CB.6050602@osean.fr>
On Mon, Feb 28, 2011 at 04:52:43PM +0100, Jean-Francois Argentino wrote:
> from JF Argentino <jf.argentino@free.fr>
>
> Adding support for the OLIMEX ARM-USB-OCD-H JTAG device (id 15ba:002b)
> based on FTDI FT2232H
> Signed-off-by: JF Argentino <jf.argentino@free.fr>
Look good, but please send this patch directly to Greg KH and CC
linux-usb as well.
Thanks,
Johan
> --- linux-2.6.37.2/drivers/usb/serial/ftdi_sio_ids.h 2011-02-25
> 00:09:00.000000000 +0100
> +++ linux/drivers/usb/serial/ftdi_sio_ids.h 2011-02-28
> 15:42:19.000000000 +0100
> @@ -730,6 +730,7 @@
> /* Olimex */
> #define OLIMEX_VID 0x15BA
> #define OLIMEX_ARM_USB_OCD_PID 0x0003
> +#define OLIMEX_ARM_USB_OCD_H_PID 0x002b
>
> /*
> * Telldus Technologies
> --- linux-2.6.37.2/drivers/usb/serial/ftdi_sio.c 2011-02-25
> 00:09:00.000000000 +0100
> +++ linux/drivers/usb/serial/ftdi_sio.c 2011-02-28 16:27:02.000000000 +0100
> @@ -721,6 +721,8 @@ static struct usb_device_id id_table_com
> { USB_DEVICE(FTDI_VID, FTDI_PROPOX_JTAGCABLEII_PID) },
> { USB_DEVICE(OLIMEX_VID, OLIMEX_ARM_USB_OCD_PID),
> .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk },
> + { USB_DEVICE(OLIMEX_VID, OLIMEX_ARM_USB_OCD_H_PID),
> + .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk },
> { USB_DEVICE(FIC_VID, FIC_NEO1973_DEBUG_PID),
> .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk },
> { USB_DEVICE(FTDI_VID, FTDI_OOCDLINK_PID),
prev parent reply other threads:[~2011-03-09 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 15:52 [PATCH] ftdi_sio: adding support for OLIMEX ARM-USB-OCD-H Jean-Francois Argentino
2011-03-09 21:13 ` Johan Hovold [this message]
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=20110309211320.GB14009@localhost \
--to=jhovold@gmail.com \
--cc=greg@kroah.com \
--cc=jf.argentino@osean.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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.