| 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: Thu, 07 Oct 2010 19:57:53 +0200 From: Johannes Berg <johannes@...solutions.net> To: Bala Shanmugam <sbalashanmugam@...eros.com> Cc: Shanmugamkamatchi Balashanmugam <Shanmugamkamatchi.Balashanmugam@...eros.com>, Luis Rodriguez <Luis.Rodriguez@...eros.com>, Marcel Holtmann <holtmann@...ux.intel.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 Thu, 2010-10-07 at 22:02 +0530, Bala Shanmugam wrote: > AR3011 when plugged-in uses PID 3000 and control goes to DFU driver [ath3k]. > ath3k downloads the firmware to the device changing its PID to 3002. > Now btusb gets the control and attaches the device to bluetooth core. > > So blacklisting 3002 in btusb will create issues for AR3011 chipsets. > In firmware if we change the PID from 3002 to 3003 as you suggested and > blacklist 3002 in btusb we can make both devices work. Yeah, that still seems like the best approach, or maybe 3004 instead of 3003 if 3003 is already in use by a different chip, or whatever. johannes -- 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