On Sun, 2014-01-19 at 18:10 -0800, Bing Zhao wrote: > Hi Ben, > > > > @@ -730,10 +730,13 @@ File: mrvl/sd8797_uapsta.bin > > > Version: 14.66.11.p151 > > > > > > File: mrvl/sd8897_uapsta.bin > > > -Version: 15.69.2.p11 > > > +Version: 15.68.201.p113 > > > > > > 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? > File: mrvl/sd8797_uapsta.bin > -Version: 14.66.11.p100 > +Version: 14.66.11.p151 > > The version is moving forward. > > But if we do, > > -Version: 14.66.11.p100 > +Version: 14.66.11.p99 > > this will be rolling backward. > > > Each firmware image contains a timestamp such as "2013/12/06, 21:28:31". > If you think that is informative I can add the timestamps in commit > logs and resend the pull request. I don't think it is. Ben. -- Ben Hutchings One of the nice things about standards is that there are so many of them.
Attachment:
signature.asc
Description: This is a digitally signed message part
