Return-Path: Subject: RE: RFC: btusb firmware load help From: Marcel Holtmann To: Shanmugamkamatchi Balashanmugam Cc: Luis Rodriguez , Johannes Berg , 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:24:32 +0200 Message-ID: <1286465072.6145.151.camel@aeonflux> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: Hi Bala, > Thanks Johannes. This would be better option to change PID in firmware > as blacklisting 3002 might create problems for 3011 chipsets. > Will try and let you people know. The misbehaving 3002 needs to be blacklisted in btusb.c anyway. However after loading the firmware to 3002 device, it should change its PID to something else. I am still trying to figure out if this is one stage firmware loading or a two stage firmware loading. This is all pretty unclear and nobody has answered this clearly so far. Regards Marcel