From: Ben Hutchings <ben@decadent.org.uk>
To: Bing Zhao <bzhao@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Frank Huang <frankh@marvell.com>
Subject: Re: linux-firmware: pull-request Marvell mwifiex-firmware 2014-01-09
Date: Mon, 20 Jan 2014 20:32:38 +0000 [thread overview]
Message-ID: <20140120203238.GT18005@decadent.org.uk> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430F53691FC8@SC-VEXCH1.marvell.com>
On Mon, Jan 20, 2014 at 12:26:47PM -0800, Bing Zhao wrote:
> Hi Ben,
>
> > > > > File: mrvl/usb8797_uapsta.bin
> > > > > -Version: 14.69.11.p179
> > > > > +Version: 14.68.29.p26
> > > > [...]
> > > >
> > > > Why are these updates rolling the version number backward? Did the
> > > > later versions cause regressions?
> > >
> > > These images are newer firmware versions actually.
> > >
> > > The 2nd (69 or 68) and 3rd (11 or 29) numbers in the version string do
> > > not necessarily mean the version increasing or decreasing. Only when
> > > first 3 numbers are fixed, a smaller 4th number will mean that the
> > > version is rolling backward. For examples,
> >
> > So what do you they mean and why are they in the version number?
>
> The first 3 numbers altogether identifies the firmware branch/features. The 4th number is the firmware revision.
This is a uniquely confusing way of generating version numbers. If
only the current 4th part (what you call firmware revision) follows
the usual version ordering, then I think that should be used as the
(public) version number.
Ben.
--
Ben Hutchings
Gates has joked that everything goes on and off unexepectedly in the house,
which is run by a high-end PC network built on Windows NT. - Seattle Times
prev parent reply other threads:[~2014-01-20 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 3:48 linux-firmware: pull-request Marvell mwifiex-firmware 2014-01-09 Bing Zhao
2014-01-19 23:39 ` Ben Hutchings
2014-01-20 2:10 ` Bing Zhao
2014-01-20 2:22 ` James Cameron
2014-01-20 20:25 ` Bing Zhao
2014-01-20 2:57 ` Ben Hutchings
2014-01-20 20:26 ` Bing Zhao
2014-01-20 20:32 ` Ben Hutchings [this message]
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=20140120203238.GT18005@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=bzhao@marvell.com \
--cc=frankh@marvell.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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).