On Mon, 22 Feb 2010, Anssi Hannula wrote: > I guess that would suggest that the device doesn't allow the initialization > data to be broken into packets arbitrarily (though some differences seem > allowed, as the windows driver transmits them differently). > > Does this mean a tty interface is ill-suited for the microcode upload, and > instead qcserial should use the kernel's generic microcode upload mechanism or > the userspace should use libusb to do it? I don't know. Didn't the old successful code use a tty interface? > Any idea what could be causing the hang, then? No idea, unless it's the device. > The WARNING that appears when > interrupting the hung gobi_loader is for serial_unthrottle() being called > while usb_serial_port->port.count == 0. That's a bogus warning. It will be removed in an upcoming kernel version. 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
