The attached patch fixes a bug introduced by myself (a brown paper bag one) when I posted the patch that introduced this same PID to the id_table_FT232BM array only and not the id_table_combined array.
(I'm sending attached because my email client mangles whitespace)
By the way, there are a lot of suspicious looking entries in these arrays that seem to use the wrong macro (USB_DEVICE vs USB_DEVICE_VER). I can build a patch to correct them, but I didn't want to do two things in one patch)
Signed-Off by: Paulo Marques <[EMAIL PROTECTED]>
-- Paulo Marques - www.grupopie.com
All that is necessary for the triumph of evil is that good men do nothing. Edmund Burke (1729 - 1797)
--- drivers/usb/serial/ftdi_sio.c.orig 2004-11-16 15:26:03.217491133 +0000
+++ drivers/usb/serial/ftdi_sio.c 2004-11-16 15:27:21.651899672 +0000
@@ -536,6 +536,7 @@ static struct usb_device_id id_table_com
{ USB_DEVICE_VER(FTDI_VID, FTDI_MTXORB_5_PID, 0x400, 0xffff) },
{ USB_DEVICE_VER(FTDI_VID, FTDI_MTXORB_6_PID, 0x400, 0xffff) },
{ USB_DEVICE_VER(FTDI_VID, FTDI_PERLE_ULTRAPORT_PID, 0x400, 0xffff) },
+ { USB_DEVICE(FTDI_VID, FTDI_PIEGROUP_PID) },
{ USB_DEVICE(SEALEVEL_VID, SEALEVEL_2101_PID) },
{ USB_DEVICE(SEALEVEL_VID, SEALEVEL_2102_PID) },
{ USB_DEVICE(SEALEVEL_VID, SEALEVEL_2103_PID) },
