On Wed, 2016-01-06 at 23:50 -0200, Jose Alonso wrote: > I will not continue with this patch. That is unfortunate. > The reasons are: > > 1. The device 04e8:6601 is used by models in update firmware: > GT-i9000 series, Galaxy Tab P1000, I5700, ... > and also used for modems!!!. Yes, this sucks. > 2. The device 04e8:68c3 is used by models in update firmware: > Droid Charge series and ?!? Well yes, but should those be driven by cdc-acm? > 3. The device 04e8:685d (GT-S6812B) that I am testing is not a > "healthy" device. > The command "lsusb -v -d 04e8:685d" prints information and > gives errors: > can't get debug descriptor: Resource temporarily unavailable > cannot read device status, Resource temporarily unavailable (11) The device is quirky. Well, we can handle that if we must. The most important question is whether we can simply go by ID in doing so. > After this the device is "locked" and must be turned off. > There is no "warranty" that 04e8:685d is only used for this purpose. > And finally, I think it's possible for someone to implement a update > firmware program using /dev/ttyACM*. > > In order to run Heimdall, I think that a better solution would be to > temporarily "blacklist" the module "cdc_acm". No. That is no solution. A user may really need cdc-acm. Your work around may cut somebody's connect to the web. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
