On Wed, Oct 06, 2010 at 11:28:17AM -0700, Johannes Berg wrote: > On Wed, 2010-10-06 at 11:26 -0700, Luis R. Rodriguez wrote: > > > > Good idea, I forgot about possible firmware changes :) Lets see if our > > > team can do that. Thanks for all the feedback. > > > > Deepak a proof of concept test can involve simply hex-editing the > > ath3k-1.fw and replacing 0x3002 to 0x3003, then the above patch might > > work. > > $ hd ath3k-1.fw > ... > 00000670 00 00 00 00 00 00 00 00 00 00 00 00 f3 0c 02 30 |...............0| > 00000680 12 01 10 01 e0 01 01 40 f3 0c 02 30 01 00 00 00 |.......@...0....| > ... > > that looks a lot like the IDs right there, in little endian :-) Furthermore another idea by johannes is that if we cannot fix this in firmware by changing the exposed device ID, we could just check in btusb for some USB component that would come alive once the firmware does get loaded, like endpoints, or speed, or whatever. But that would be last resort. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
