Return-Path: <cyrus@holtmann.org>
Date: Sat, 9 Oct 2010 00:47:37 +0200 (CEST)
From: Sven-Haegar Koch <haegar@sdinet.de>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
cc: Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
    Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
    David Woodhouse <dwmw2@infradead.org>,
    Marcel Holtmann <marcel@holtmann.org>,
    linux-bluetooth <linux-bluetooth@vger.kernel.org>,
    "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
    linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Firmware versioning best practices: ath3k-2.fw rename or replace
 ath3k-1.fw ?
In-Reply-To: <20101008181508.GM10149@tux>
Message-ID: <alpine.DEB.2.02.1010090040240.19472@aurora.sdinet.de>
References: <20101008170258.GJ10149@tux> <4CAF5488.3030706@Atheros.com> <20101008181508.GM10149@tux>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
List-ID: <linux-bluetooth.vger.kernel.org>

On Fri, 8 Oct 2010, Luis R. Rodriguez wrote:

> > > I last tried to document a thread we had over this here:
> > >
> > > http://wireless.kernel.org/en/developers/Documentation/firmware-versioning
> > >
> 
> Thanks, I've updated that link above to document bug fixing does not require
> a filename change.

I would summarize it as:

If a new firmware version also works with an old driver, keep the filename.

If a new firmware version also requires a new driver, change the name.

If a new driver requires a new firmware, change the name.

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.