lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 6 Oct 2010 11:22:13 -0700 From: "Luis R. Rodriguez" <lrodriguez@...eros.com> To: Johannes Berg <johannes@...solutions.net> Cc: Marcel Holtmann <holtmann@...ux.intel.com>, Luis Rodriguez <Luis.Rodriguez@...eros.com>, linux-bluetooth <linux-bluetooth@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, Deepak Dhamdhere <Deepak.Dhamdhere@...eros.com>, Sree Durbha <Sree.Durbha@...eros.com> Subject: Re: RFC: btusb firmware load help On Wed, Oct 6, 2010 at 10:54 AM, Johannes Berg <johannes@...solutions.net> 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-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists