On Mon, 11 Jan 2010, John Ervin wrote: > Hello, > > Been writing a kernel driver to access an fx2 based board and having some > trouble. I'd like to download vendor firmware into this but it wasn't coming up > after the firmware download/reset (did the typical external first, inactivate > internal codes next, full reset). So as a test I wanted to just reset (toggling > cpu_regs 1 then 0) the base firmware (which has A3 support, the 'FX2 Loader' > firmware). The device then started misbehaving. You're using the word "reset" to mean several different things. Can you be more explicit? > After this simple reset, I could no longer get the configuration descriptor, as > I could before reset (no data, -61, returned for usb_get_descriptor(dev->udev, > USB_DT_CONFIG, 0, dev->config_descriptor, sizeof(*dev->config_descriptor) ). The > strange thing here, is that /proc/bus/usb/devices has the configuration > information, as does Sysfs. > > Though I don't understand the call, a call to: > > usb_reset_configuration(dev->udev); > > after reset did not fix the problem. usb_reset_configuration() probably doesn't do what you think. In general drivers should avoid using it. It was created mainly for usbfs. > Anyone know how to get this simple reset to bring the device back to a > query-able state? What sort of "simple reset" do you want to do? A USB port reset? And in what context do you want to do it? The driver's probe() routine? Alan Stern -- 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
