Return-path: Received: from mail.atheros.com ([12.19.149.2]:24456 "EHLO mail.atheros.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750893Ab0JNEXF (ORCPT ); Thu, 14 Oct 2010 00:23:05 -0400 Message-ID: <4CB685A4.8030301@Atheros.com> Date: Thu, 14 Oct 2010 09:53:00 +0530 From: Suraj Sumangala MIME-Version: 1.0 To: "Luis R. Rodriguez" CC: Kevin Hayes , Luis Rodriguez , Marcel Holtmann , "Henry Ptasinski" , Suraj Sumangala , David Woodhouse , linux-bluetooth , "linux-kernel@vger.kernel.org" , linux-wireless Subject: Re: Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ? References: <20101008170258.GJ10149@tux> <4CAF5488.3030706@Atheros.com> <20101008181508.GM10149@tux> <20101012211726.GE2678@broadcom.com> <1286964370.3316.6.camel@aeonflux> In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Luis, On 10/13/2010 11:39 PM, Luis R. Rodriguez wrote: > Does HCI support uploading firmware? Can't we resolve this blacklist > crap issue if devices just used HCI to upload firmware? HCI does not support uploading firmware. But HCI does provide options for vendor specific commands that can be used for uploading firmware as long as your device has enough intelligence to understand the command when it comes. This is what we do for AR300x serial devices. We do not download firmware, but we do download all configuration entries as VS HCI commands. > > Luis Regards Suraj