From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
David Woodhouse <dwmw2@infradead.org>,
Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ?
Date: Fri, 8 Oct 2010 10:02:59 -0700 [thread overview]
Message-ID: <20101008170258.GJ10149@tux> (raw)
Suraj,
What is the difference between ath3k-2.fw and ath3k-1.fw ?
Won't the API change now that you are addressing the sflash
configuration fix? Would it not help to identify the two
different firmwares then?
David, Marcel, what are your preferences for a firmware upgrade
where the firmware does not change API (lets just pretend it does
not for a moment) ? Do we keep the same filename?
In this particular case I would assume our new sflash configuration
fix that might be being worked on might change the re-enumerated
USB device IDs so it seems to me a good idea to use a new filename.
I should note ath3k-2.fw already made it to linux-firmware.git...
I last tried to document a thread we had over this here:
http://wireless.kernel.org/en/developers/Documentation/firmware-versioning
Does this sound sane? If so then the sflash configuration fix
would seem to me like it would require a new filename. Now, while
we're at it, how about bug fixes?
Suraj -- keep these discussions public please....
Luis
next reply other threads:[~2010-10-08 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 17:02 Luis R. Rodriguez [this message]
2010-10-08 17:27 ` Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ? Suraj Sumangala
2010-10-08 18:15 ` Luis R. Rodriguez
2010-10-08 22:47 ` Sven-Haegar Koch
2010-10-09 8:06 ` Marcel Holtmann
2010-10-12 21:17 ` Henry Ptasinski
2010-10-13 10:06 ` Marcel Holtmann
2010-10-13 17:42 ` Luis R. Rodriguez
2010-10-13 17:54 ` Kevin Hayes
2010-10-13 18:09 ` Luis R. Rodriguez
2010-10-13 18:41 ` Kevin Hayes
2010-10-14 4:23 ` Suraj Sumangala
2010-10-09 8:01 ` Marcel Holtmann
2010-10-11 7:14 ` Senthil Balasubramanian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101008170258.GJ10149@tux \
--to=lrodriguez@atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=dwmw2@infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).