From: Christian Lamparter <chunkeey@googlemail.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
"ath9k_htc_fw" <ath9k_htc_fw@lists.infradead.org>,
"linux-wireless" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-bluetooth" <linux-bluetooth@vger.kernel.org>
Subject: Re: Version number policy!
Date: Fri, 5 Apr 2013 19:03:09 +0200 [thread overview]
Message-ID: <201304051903.11215.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAB=NE6V3sApMSGWkKbaFaJC4+VpLxgYF-xyNRKxiA-YDCwhGkQ@mail.gmail.com>
On Friday 05 April 2013 10:19:00 Luis R. Rodriguez wrote:
> On Thu, Apr 4, 2013 at 11:27 AM, Adrian Chadd <adrian@freebsd.org> wrote:
> > Here's my first take on the version number policy:
> >
> > https://github.com/qca/open-ath9k-htc-firmware/wiki/VersionPolicy
> > The summary:
> >
> > * major version number changes are for firmware API / behaviour
> > changes that aren't backwards compatible;
> > * minor version number changes are for firmware API / behaviour
> > changes that are incremental and default to the old behaviour (eg, new
> > optional commands);
> > * the driver should check the minor version number before using any
> > optional features with that version.
> >
> > What's TODO:
> >
> > * Add a new WMI command to get the build number, git string, etc.
> > * add it as our first optional minor version command :-)
>
> This is better than anything we had drafted before for 802.11 open
> firmware design rules. Cc'ing a few lists for wider review given that
> what we had written before for rules was for 802.11 and Bluetooth [0]
> and it was very Linux specific. We are striving for open firmware here
> for the community, for BSD / Linux. Christian would have dealt with
> more of the support on open firmware design so far due to carl9170.fw
> [1] so curious if he has any input.
Based on my experience with carl9170, I can tell you that
new stuff (new wmi commands, or advanced offload caps, features
and bugfixes) should be advised via feature flags in bitmaps
and not firmware versions. [Just make it long enough...]
Otherwise you'll have to write endless checks like:
if ((fw_minor == 1 && fw_patch > 30) ||
(fw_minor == 2 && fw_patch > 7) ||
(fw_minor == 3 && fw_patch > 3) ||
(fw_minor > 4))
feature_supported = true;
everytime you backport features and bugfixes to older firmwares.
Also, firmware dates are more important than you think.
They allow some way of syncing the firmware->driver and
your inbox.
Regards,
Christian
next prev parent reply other threads:[~2013-04-05 17:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ-Vmo=LVSzdEo6DhfOVT_0JHCTMmdPU1zGfMuBmhmr8QuDmJQ@mail.gmail.com>
2013-04-05 8:19 ` Version number policy! Luis R. Rodriguez
2013-04-05 8:21 ` Adrian Chadd
2013-04-05 16:42 ` Eugene Krasnikov
2013-04-05 17:03 ` Christian Lamparter [this message]
2013-04-05 17:23 ` Eugene Krasnikov
2013-04-05 18:08 ` Christian Lamparter
2013-04-05 19:16 ` Adrian Chadd
2013-04-06 5:52 ` Kalle Valo
2013-04-06 7:08 ` Adrian Chadd
2013-04-08 9:10 ` Eugene Krasnikov
2013-04-08 15:33 ` Christian Lamparter
2013-04-08 19:00 ` Adrian Chadd
2013-04-08 20:37 ` Eugene Krasnikov
2013-04-08 22:03 ` Christian Lamparter
2013-04-08 23:12 ` Adrian Chadd
2013-04-09 0:37 ` Theodore Ts'o
2013-04-09 1:51 ` Adrian Chadd
2013-04-09 11:28 ` Theodore Ts'o
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=201304051903.11215.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=adrian@freebsd.org \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
/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).