* [PATCH] New ID for ftdi_sio
@ 2004-04-08 16:51 Kronos
2004-04-09 19:14 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Kronos @ 2004-04-08 16:51 UTC (permalink / raw)
To: linux-kernel; +Cc: greg
Hi,
I have an USB contactless reader which uses a FTDI chip. It works well with the
current ftdi_sio driver, it's just a matter of adding an ID:
--- linux-2.6/drivers/usb/serial/ftdi_sio.h.orig 2004-04-08 18:24:22.000000000 +0200
+++ linux-2.6/drivers/usb/serial/ftdi_sio.h 2004-04-08 18:29:26.000000000 +0200
@@ -162,6 +162,9 @@
#define PROTEGO_SPECIAL_3 0xFC72 /* special/unknown device */
#define PROTEGO_SPECIAL_4 0xFC73 /* special/unknown device */
+/* Inside Accesso contactless reader (http://www.insidefr.com) */
+#define INSIDE_ACCESSO 0xFAD0
+
/* Commands */
#define FTDI_SIO_RESET 0 /* Reset the port */
#define FTDI_SIO_MODEM_CTRL 1 /* Set the modem control register */
--- linux-2.6/drivers/usb/serial/ftdi_sio.c.orig 2004-04-08 18:23:41.000000000 +0200
+++ linux-2.6/drivers/usb/serial/ftdi_sio.c 2004-04-08 18:27:50.000000000 +0200
@@ -354,6 +354,7 @@
{ USB_DEVICE_VER(FTDI_VID, PROTEGO_SPECIAL_3, 0, 0x3ff) },
{ USB_DEVICE_VER(FTDI_VID, PROTEGO_SPECIAL_4, 0, 0x3ff) },
{ USB_DEVICE_VER(FTDI_VID, FTDI_ELV_UO100_PID, 0, 0x3ff) },
+ { USB_DEVICE_VER(FTDI_VID, INSIDE_ACCESSO, 0, 0x3ff) },
{ } /* Terminating entry */
};
@@ -532,6 +533,7 @@
{ USB_DEVICE(FTDI_VID, PROTEGO_SPECIAL_3) },
{ USB_DEVICE(FTDI_VID, PROTEGO_SPECIAL_4) },
{ USB_DEVICE(FTDI_VID, FTDI_ELV_UO100_PID) },
+ { USB_DEVICE(FTDI_VID, INSIDE_ACCESSO) },
{ } /* Terminating entry */
};
This is the output of lsusb:
Bus 002 Device 002: ID 0403:fad0 Future Technology Devices International, Ltd
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 0xfad0
bcdDevice 2.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 100mA
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
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 bytes 64 once
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 bytes 64 once
bInterval 0
Please apply.
Luca
--
Home: http://kronoz.cjb.net
"It is more complicated than you think"
-- The Eighth Networking Truth from RFC 1925
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] New ID for ftdi_sio
2004-04-08 16:51 [PATCH] New ID for ftdi_sio Kronos
@ 2004-04-09 19:14 ` Greg KH
2004-04-10 15:41 ` Kronos
0 siblings, 1 reply; 4+ messages in thread
From: Greg KH @ 2004-04-09 19:14 UTC (permalink / raw)
To: Kronos; +Cc: linux-kernel
On Thu, Apr 08, 2004 at 06:51:23PM +0200, Kronos wrote:
> Hi,
> I have an USB contactless reader which uses a FTDI chip. It works well with the
> current ftdi_sio driver, it's just a matter of adding an ID:
Ick, this patch doesn't apply due to all of the recent ids being added
to this driver. Can you re-diff it against the latest -mm tree and
resend it to me?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] New ID for ftdi_sio
2004-04-09 19:14 ` Greg KH
@ 2004-04-10 15:41 ` Kronos
2004-04-12 23:36 ` Greg KH
0 siblings, 1 reply; 4+ messages in thread
From: Kronos @ 2004-04-10 15:41 UTC (permalink / raw)
To: Greg KH; +Cc: linux-kernel
Il Fri, Apr 09, 2004 at 12:14:50PM -0700, Greg KH ha scritto:
> On Thu, Apr 08, 2004 at 06:51:23PM +0200, Kronos wrote:
> > Hi,
> > I have an USB contactless reader which uses a FTDI chip. It works well with the
> > current ftdi_sio driver, it's just a matter of adding an ID:
>
> Ick, this patch doesn't apply due to all of the recent ids being added
> to this driver. Can you re-diff it against the latest -mm tree and
> resend it to me?
Here it is:
--- linux-2.6/drivers/usb/serial/ftdi_sio.h.orig 2004-04-10 17:35:27.000000000 +0200
+++ linux-2.6/drivers/usb/serial/ftdi_sio.h 2004-04-10 17:36:47.000000000 +0200
@@ -191,6 +191,9 @@
#define LINX_FUTURE_1_PID 0xF44B /* Linx future device */
#define LINX_FUTURE_2_PID 0xF44C /* Linx future device */
+/* Inside Accesso contactless reader (http://www.insidefr.com) */
+#define INSIDE_ACCESSO 0xFAD0
+
/* Commands */
#define FTDI_SIO_RESET 0 /* Reset the port */
#define FTDI_SIO_MODEM_CTRL 1 /* Set the modem control register */
--- linux-2.6/drivers/usb/serial/ftdi_sio.c.orig 2004-04-10 17:36:52.000000000 +0200
+++ linux-2.6/drivers/usb/serial/ftdi_sio.c 2004-04-10 17:38:07.000000000 +0200
@@ -354,6 +354,7 @@
{ USB_DEVICE_VER(FTDI_VID, PROTEGO_SPECIAL_3, 0, 0x3ff) },
{ USB_DEVICE_VER(FTDI_VID, PROTEGO_SPECIAL_4, 0, 0x3ff) },
{ USB_DEVICE_VER(FTDI_VID, FTDI_ELV_UO100_PID, 0, 0x3ff) },
+ { USB_DEVICE_VER(FTDI_VID, INSIDE_ACCESSO, 0, 0x3ff) },
{ } /* Terminating entry */
};
@@ -558,6 +559,7 @@
{ USB_DEVICE_VER(FTDI_VID, LINX_FUTURE_0_PID, 0x400, 0xffff) },
{ USB_DEVICE_VER(FTDI_VID, LINX_FUTURE_1_PID, 0x400, 0xffff) },
{ USB_DEVICE_VER(FTDI_VID, LINX_FUTURE_2_PID, 0x400, 0xffff) },
+ { USB_DEVICE(FTDI_VID, INSIDE_ACCESSO) },
{ } /* Terminating entry */
};
Luca
--
Home: http://kronoz.cjb.net
Al termine di un pranzo di nozze mi hanno dato un
amaro alle erbe cosi' schifoso che perfino sull'etichetta
c'era un frate che vomitava.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] New ID for ftdi_sio
2004-04-10 15:41 ` Kronos
@ 2004-04-12 23:36 ` Greg KH
0 siblings, 0 replies; 4+ messages in thread
From: Greg KH @ 2004-04-12 23:36 UTC (permalink / raw)
To: Kronos; +Cc: linux-kernel
On Sat, Apr 10, 2004 at 05:41:07PM +0200, Kronos wrote:
> Il Fri, Apr 09, 2004 at 12:14:50PM -0700, Greg KH ha scritto:
> > On Thu, Apr 08, 2004 at 06:51:23PM +0200, Kronos wrote:
> > > Hi,
> > > I have an USB contactless reader which uses a FTDI chip. It works well with the
> > > current ftdi_sio driver, it's just a matter of adding an ID:
> >
> > Ick, this patch doesn't apply due to all of the recent ids being added
> > to this driver. Can you re-diff it against the latest -mm tree and
> > resend it to me?
>
> Here it is:
Looks good, thanks. I've applied this to my trees and will send it off
in the next round of updates.
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-04-12 23:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-04-08 16:51 [PATCH] New ID for ftdi_sio Kronos
2004-04-09 19:14 ` Greg KH
2004-04-10 15:41 ` Kronos
2004-04-12 23:36 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®