> Greg KH <greg@kroah.com> writes:[]>> Please work to see what is wrong with the existing patch. Is there>> anything that I can do to help you out?>> This thing has consumed something like sixteen hours of my life in> total, with a gain-to-be-expected of exactly zero (I don't need to run> 'current' kernels on my work machine, I have just grown into the habit> of doing so) and those sixteen hours cannot come back (and I even have> had these type of discussions around 'should it rather look like math> or rather like text' in sufficent quantities :->), so, except that I> would be very much obliged to you if a fix for this issue could go> into the 'official' tree rather sooner than later, no.

In short, it turned, that usb drivers aren't drivers at all, they arejust "USB interface drivers", i.e. managers of the particular USBinterface *in* the device.

Problem is: after changing ti-usb-serial's firmware, it is being resetand apears with new device ID. It's OK so far, but even this may bebetter (from USB hardware implementation point of view). Then thisdevice, after being caught with new ID by the same "driver" requiresseting USB configuration #2, in order to be usb-serial converter. Day waslost to make this happen _inside_ driver (kernel 2.6.18). It turned, thatonly way to do so is SYSFS, that set up by udev, and"usb_set_configuration()" function is being used for that.

And don't say, USB device requires userspace to setup (externalfirmware is another question). I can be young and stupid, and this isvery wired only for my understanding. Simple NULL by default or settable of {num_usb_conf, num_interface} for "drivers" will be enough.> Apart from that, I make a (fairly miserable) living by adapting open> source code to be usable in specific situations (ie adding or> modifying features, fixing bugs, writing drivers etc)

So and i. I wanted to adopt request_firmware() for TI USB serial, buti became very confused and upset.