Return-Path: Subject: RE: RFC: btusb firmware load help From: Johannes Berg To: Shanmugamkamatchi Balashanmugam Cc: Luis Rodriguez , Marcel Holtmann , linux-bluetooth , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , Deepak Dhamdhere , Sree Durbha In-Reply-To: <44EE5C37ADC36343B0625A05DD408C4850DAD2CA31@CHEXMB-01.global.atheros.com> References: <1286349552.6145.11.camel@aeonflux> <1286380566.6145.42.camel@aeonflux> <20101006163816.GE7070@tux> <20101006173949.GG7070@tux> <1286387660.3655.382.camel@jlt3.sipsolutions.net> <1286389697.3655.401.camel@jlt3.sipsolutions.net> ,<20101006183340.GI7070@tux> <44EE5C37ADC36343B0625A05DD408C4850DAD2CA31@CHEXMB-01.global.atheros.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 07 Oct 2010 17:15:55 +0200 Message-ID: <1286464555.20974.3.camel@jlt3.sipsolutions.net> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: > Thanks Johannes. This would be better option to change PID in firmware > as blacklisting 3002 might create problems for 3011 chipsets. What would be the problem with 3011? Does it also use the 3002 ID, but not use firmware upload??? johannes