On Tue, Sep 4, 2012 at 8:15 AM, Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote: > On Sun, Sep 02, 2012 at 01:55:56PM -0400, Kevin McKinney wrote: >> This patch replaces an invalid device id of 0x132 >> with the correct device id of 0x172 as reported >> by Rinat Camalov <richman1000000d@xxxxxxxxx>. >> > > It could be that both IDs are valid. It wouldn't hurt to leave the > old one in until we were certain. > > -#define BCM_USB_PRODUCT_ID_226 0x0132 > +#define BCM_USB_PRODUCT_ID_226 0x0132 /* not sure if this is valid */ > +#define BCM_USB_PRODUCT_ID_ZTE_226 0x0172 > > Then add it to the InterfaceUsbtable[] array at the top of > drivers/staging/bcm/InterfaceInit.c Sure, makes sense. I will submit another patch to include this. > Also I would be interested to know if Rinat was actually able to get > the device to work or was it only loading. Rinat, Were you able to get the device working? Thanks, Kevin _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
