On Wed, Oct 6, 2010 at 10:54 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Wed, 2010-10-06 at 10:39 -0700, Luis R. Rodriguez wrote: > > >> > With sflash based AR3011 hardware, when we connect the device to USB >> > port it gets detected as a Bluetooth device because of firmware in >> > Flash (VID=0x0CF3, PID=0x3002). This triggers the Bluetooth sub >> > system driver (btusb.ko) directly in the host instead of ath3k >> > DFU driver. Therefore, there is no firmware downloaded in to the >> > RAM to bring up Bluetooth at this point. This is the problem >> > we're trying to "fix". > > So the easiest fix for this would be to > Âa) ignore 0x0cf3,0x3002 in btusb > Âb) add it to ath3k firmware loading > Âc) change the ath3k firmware to load with 0x0cf3,0x3003 (or whatever > Â Âelse you want, as long as it's not 0x3000 and not 0x3002) > > Then the ignore in btusb won't affect ath3k after that new firmware was > loaded. Good idea, I forgot about possible firmware changes :) Lets see if our team can do that. Thanks for all the feedback. 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
