On Tuesday 05 February 2008, Alan Nisota wrote: > >> Try to patch max_packet(maxp) into it and see if that works. > >> Use the interrupt case for guidance. > ... > > Well, this hack allows me to read without babble on my newer machines, > but the one I really need it to work on has an older motherboard, and > refuses to accept the 1024 byte packets. I'll need to either work iwth > the vendor or see if I can patch the firmware.
Try to get the vendor to fix their broken product. I'm fairly sure it can't be certified as USB-compliant that way ... > Thanks for the help.searching the archives I saw this isn't that > uncommon of a problem, Well, it's been reported once before, as I recall. Maybe even for the same vendor's product. > and there was talk of adding a switch to the > module to allow these out-of-spec devices to work via a similar fix. Is > there anything I could do to move that along? Send the patch for that one line hack, that's a start. A module parameter would be pointless. The missing part, other than that one-line hack, would be adding code to the descriptor parsing to detect this specific bogosity and then warning about it. The thing is that in this specific case it's easy to partially work around the vendor bug. Not all the high speed HCDs will necessarily do that, though. - Dave - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
