Hi,
Am Sonntag 30 März 2008 schrieb Jean Delvare:
> > Does this make sense?
>
> Yes it does, thanks for clarifying. Please send an updated patch and
> I'll apply it.
Please find a new patch attached.
> Do you plan to phase out the old VID/PID pair? If so, I'll have to send
> you back my i2c-tiny-usb device for a firmware update.
Nothing will change for people using the old vid/pid pair as the driver still
supports that and i don't think there's a reason to also remove
the old vid/pid pair from the driver. But since you don't have the latest
firmware, you might of course return your device anyway to get it updated.
It'll then be detected correctly if it's plugged in at boot time.
Till
So here we go:
This patch adds support for the EZPrototypes USB vid/pid pair used in later
i2c-tiny-usb firmware versions (avrusb v1.06 and up, usbtiny v2.06 and up).
Signed-off-by: Till Harbaum <[EMAIL PROTECTED]>
--- linux-2.6.24.3.orig/drivers/i2c/busses/i2c-tiny-usb.c 2008-02-26 01:20:20.000000000 +0100
+++ linux-2.6.24.3/drivers/i2c/busses/i2c-tiny-usb.c 2008-03-30 20:47:46.000000000 +0200
@@ -131,11 +131,15 @@
/* ----- begin of usb layer ---------------------------------------------- */
-/* The usb i2c interface uses a vid/pid pair donated by */
-/* Future Technology Devices International Ltd. */
+/*
+ * Initially the usb i2c interface uses a vid/pid pair donated by
+ * Future Technology Devices International Ltd., later a pair was
+ * bought from EZPrototypes
+ */
static struct usb_device_id i2c_tiny_usb_table [] = {
- { USB_DEVICE(0x0403, 0xc631) },
- { } /* Terminating entry */
+ { USB_DEVICE(0x0403, 0xc631) }, /* FTDI */
+ { USB_DEVICE(0x1c40, 0x0534) }, /* EZPrototypes */
+ { } /* Terminating entry */
};
MODULE_DEVICE_TABLE(usb, i2c_tiny_usb_table);
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
