From patchwork Wed Oct 6 16:38:16 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Luis Rodriguez X-Patchwork-Id: 236361 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter1.kernel.org (8.14.4/8.14.3) with ESMTP id o96GckUN024905 for ; Wed, 6 Oct 2010 16:38:47 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757426Ab0JFQiT (ORCPT ); Wed, 6 Oct 2010 12:38:19 -0400 Received: from mail.atheros.com ([12.19.149.2]:34551 "EHLO mail.atheros.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753348Ab0JFQiS (ORCPT ); Wed, 6 Oct 2010 12:38:18 -0400 Received: from mail.atheros.com ([10.10.20.108]) by sidewinder.atheros.com for ; Wed, 06 Oct 2010 09:38:10 -0700 Received: from tux (10.10.11.177) by SC1EXHC-02.global.atheros.com (10.10.20.106) with Microsoft SMTP Server (TLS) id 8.2.213.0; Wed, 6 Oct 2010 09:38:16 -0700 Received: by tux (sSMTP sendmail emulation); Wed, 06 Oct 2010 09:38:16 -0700 Date: Wed, 6 Oct 2010 09:38:16 -0700 From: "Luis R. Rodriguez" To: Marcel Holtmann CC: Luis Rodriguez , linux-bluetooth , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , Deepak Dhamdhere , Sree Durbha Subject: Re: RFC: btusb firmware load help Message-ID: <20101006163816.GE7070@tux> References: <20100924230730.GB6566@tux> <1286266981.17473.33.camel@aeonflux> <20101005192814.GB11831@tux> <1286308731.2588.13.camel@aeonflux> <1286349552.6145.11.camel@aeonflux> <1286380566.6145.42.camel@aeonflux> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1286380566.6145.42.camel@aeonflux> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (demeter1.kernel.org [140.211.167.41]); Wed, 06 Oct 2010 16:38:47 +0000 (UTC) differences between these firmware but I do remember reading from Vikram that no new API was changed. I asked for clarification on the firmware updates and asked if it can be documented here: http://wireless.kernel.org/en/users/Drivers/ath3k If the device can live with simply getting ath3k-1.fw loaded once then perhaps the change you described above is all that is needed, not sure. Deepak, can you please try this patch, I don't have hardware to test this with. diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index d22ce3c..a62c1b2 100644 --- a/drivers/bluetooth/btusb.c +++ b/drivers/bluetooth/btusb.c @@ -140,6 +140,9 @@ static struct usb_device_id blacklist_table[] = { /* Frontline ComProbe Bluetooth Sniffer */ { USB_DEVICE(0x16d3, 0x0002), .driver_info = BTUSB_SNIFFER }, + /* Atheros AR3011 without firmware */ + { USB_DEVICE(0x0cf3, 0x3002), .driver_info = BTUSB_IGNORE }, + { } /* Terminating entry */ };