On Thu, Apr 20, 2017 at 04:43:49PM +0200, Alfredo Rafael Vicente Boix wrote: > Hello, > > I have tried your patch and it works fine. It seems that it recognised > the tower and also creates the path /dev/usb/legousbtower0. > > [ 784.308089] usb 8-2: new low-speed USB device number 4 using uhci_hcd > [ 784.529202] usb 8-2: New USB device found, idVendor=0694, idProduct=0001 > [ 784.529205] usb 8-2: New USB device strings: Mfr=4, Product=26, > SerialNumber=0 > [ 784.529208] usb 8-2: Product: LEGO USB Tower > [ 784.529210] usb 8-2: Manufacturer: LEGO Group > [ 784.537094] legousbtower 8-2:1.0: LEGO USB Tower firmware version > is 1.0 build 134 > [ 784.538146] legousbtower 8-2:1.0: LEGO USB Tower #-160 now attached > to major 180 minor 0 > > But when I tried to access it with nqc (sudo nqc > -S/dev/usb/legousbtower0 -firmware ./firm0332.lgo), for example, it > gives me the following error: > > Could not open serial port or USB device. > > with the log: > > [ 784.538146] legousbtower 8-2:1.0: LEGO USB Tower #-160 now attached > to major 180 minor 0 > [ 994.013492] usb 8-2: LEGO USB Tower reset control request failed Oh good! That means you must have the VIRTUAL STACK configuration option enabled. The driver is trying to send USB messages off of the stack instead of dynamically allocating them. This request error is also a symptom of that. I'll work on a patch for all of the parts of this driver that have that issue and send it to you in a bit... thanks, greg k-h -- 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
