Hi,
Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
Series
WiFi Adapter is now available for download from
http://intellinuxwireless.org/?n=Downloads
Changes:
- Fix "tid mismatch" issue
Wey-Yi
2011/4/5 Luis R. Rodriguez <[email protected]>:
> On Mon, Apr 4, 2011 at 12:34 PM, Guy, Wey-Yi <[email protected]> wrote:
>> Changes:
>> - Fix "tid mismatch" issue
>
> What does this mean? What "tid mismatch issue"?
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214
--
Rafał
On Mon, Apr 4, 2011 at 12:34 PM, Guy, Wey-Yi <[email protected]> wrote:
> Changes:
> - Fix "tid mismatch" issue
What does this mean? What "tid mismatch issue"?
Luis
On Wed, 2011-04-06 at 10:12 -0400, John W. Linville wrote:
> On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
> > Hi,
> >
> > Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
> > Series
> > WiFi Adapter is now available for download from
> > http://intellinuxwireless.org/?n=Downloads
> >
> > Changes:
> > - Fix "tid mismatch" issue
> >
> > Wey-Yi
>
> Hmmm...the previous release was 128.50.3.1...
>
> I realize that the API portion advanced from 3.1 to 5.1, but the
> overall release number appears to be moving backwards. Is this
> intentional?
They're all over the place and basically random ... I *think* they
depend on the branch it comes from internally, but I'm not even sure.
johannes
On Wed, 2011-04-06 at 07:27 -0700, John W. Linville wrote:
> On Wed, Apr 06, 2011 at 04:24:30PM +0200, Johannes Berg wrote:
> > On Wed, 2011-04-06 at 10:12 -0400, John W. Linville wrote:
> > > On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
> > > > Hi,
> > > >
> > > > Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
> > > > Series
> > > > WiFi Adapter is now available for download from
> > > > http://intellinuxwireless.org/?n=Downloads
> > > >
> > > > Changes:
> > > > - Fix "tid mismatch" issue
> > > >
> > > > Wey-Yi
> > >
> > > Hmmm...the previous release was 128.50.3.1...
> > >
> > > I realize that the API portion advanced from 3.1 to 5.1, but the
> > > overall release number appears to be moving backwards. Is this
> > > intentional?
> >
> > They're all over the place and basically random ... I *think* they
> > depend on the branch it comes from internally, but I'm not even sure.
>
> OK, I can cope. But if you (i.e. your team) can influence them
> towards a sane numbering scheme, it will probably make packagers
> and/or release engineers happier in the distros...
>
I will give feedback to our build engineer team, thanks
Wey
On Wed, 2011-04-06 at 20:49 +0200, Gábor Stefanik wrote:
> >> OK, I can cope. But if you (i.e. your team) can influence them
> >> towards a sane numbering scheme, it will probably make packagers
> >> and/or release engineers happier in the distros...
> Perhaps formatting the number as "3.1.128.50" and "5.1.39.31" would be
> a saner idea.
It still wouldn't be monotonically increasing ... you could have
5.1.39.31 and then 5.1.17.168 since the API version doesn't necessarily
change all the time.
johannes
SGkgTHVpcywNCg0KVGhpcyAxMDAwIHVDb2RlIGFkZHJlc3MgdGhlIHNpbWlsYXIgcHJvYmxlbSB3
ZSBoYXZlIHdpdGggNTAwMCB1Q29kZShpd2x3aWZpLTUwMDAtdWNvZGUtOC4yNC4yLjEyLnRneik6
IHRoZSB1Q29kZSBtaXMtYmVoYXZlIG9uIEFNUERVIHRyYW5zbWlzc2lvbiBhbmQgc2VuZCBib2d1
cyBDb21wcmVzc2VkLUFDSyBiYWNrIHRvIGRyaXZlciB3aXRoIGludmFsaWQgdGlkIHdoaWNoIGNh
dXNlIDExbiB0aHJvdWdocHV0IGRyb3Agb3IgZGlzY29ubmVjdC4NCldlIHJlbGVhc2UgbWFpbnRl
bmFuY2UgcmVsZWFzZSBvZiA1MDAwIHVDb2RlKGl3bHdpZmktNTAwMC11Y29kZS04LjgzLjUuMS50
Z3opIGluIEZlYi4gMjAxMS4gVGhpcyBpcyB0aGUgc2FtZSBmaXggdG8gYWRkcmVzcyB0aGUgc2Ft
ZSBwcm9ibGVtIGZvciAxMDAwIHNlcmllcw0KaHR0cDovL2ludGVsbGludXh3aXJlbGVzcy5vcmcv
P249RG93bmxvYWRzDQoNCg0KVGhhbmtzDQpXZXkNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEx1aXMgUi4gUm9kcmlndWV6IFttYWlsdG86bWNncm9mQGdtYWlsLmNvbV0NClNl
bnQ6IE1vbmRheSwgQXByaWwgMDQsIDIwMTEgNDozOCBQTQ0KVG86IEd1eSwgV2V5LVlpIFcNCkNj
OiBsaW51eC13aXJlbGVzc0B2Z2VyLmtlcm5lbC5vcmc7IEZlbGl4IEZpZXRrYXUNClN1YmplY3Q6
IFJlOiBuZXcgbWFpbnRlbmFuY2UgcmVsZWFzZSBvZiBpd2x3aWZpIDEwMDAgdUNvZGUgYXZhaWxh
YmxlDQoNCk9uIE1vbiwgQXByIDQsIDIwMTEgYXQgMTI6MzQgUE0sIEd1eSwgV2V5LVlpIDx3ZXkt
eWkudy5ndXlAaW50ZWwuY29tPiB3cm90ZToNCj4gICAgICAgIENoYW5nZXM6DQo+ICAgICAgICAt
IEZpeCAidGlkIG1pc21hdGNoIiBpc3N1ZQ0KDQpXaGF0IGRvZXMgdGhpcyBtZWFuPyBXaGF0ICJ0
aWQgbWlzbWF0Y2ggaXNzdWUiPw0KDQogIEx1aXMNCg==
On Wed, Apr 6, 2011 at 4:24 PM, Guy, Wey-Yi <[email protected]> wrote:
> On Wed, 2011-04-06 at 07:27 -0700, John W. Linville wrote:
>> On Wed, Apr 06, 2011 at 04:24:30PM +0200, Johannes Berg wrote:
>> > On Wed, 2011-04-06 at 10:12 -0400, John W. Linville wrote:
>> > > On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
>> > > > Hi,
>> > > >
>> > > > ? ? ? ? Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
>> > > > ? ? ? ? Series
>> > > > ? ? ? ? WiFi Adapter is now available for download from
>> > > > ? ? ? ? http://intellinuxwireless.org/?n=Downloads
>> > > >
>> > > > ? ? ? ? Changes:
>> > > > ? ? ? ? - Fix "tid mismatch" issue
>> > > >
>> > > > ? ? ? ? Wey-Yi
>> > >
>> > > Hmmm...the previous release was 128.50.3.1...
>> > >
>> > > I realize that the API portion advanced from 3.1 to 5.1, but the
>> > > overall release number appears to be moving backwards. ?Is this
>> > > intentional?
>> >
>> > They're all over the place and basically random ... I *think* they
>> > depend on the branch it comes from internally, but I'm not even sure.
>>
>> OK, I can cope. ?But if you (i.e. your team) can influence them
>> towards a sane numbering scheme, it will probably make packagers
>> and/or release engineers happier in the distros...
>>
> I will give feedback to our build engineer team, thanks
>
> Wey
>
Perhaps formatting the number as "3.1.128.50" and "5.1.39.31" would be
a saner idea.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
On Wed, 2011-04-06 at 07:12 -0700, John W. Linville wrote:
> On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
> > Hi,
> >
> > Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
> > Series
> > WiFi Adapter is now available for download from
> > http://intellinuxwireless.org/?n=Downloads
> >
> > Changes:
> > - Fix "tid mismatch" issue
> >
> > Wey-Yi
>
> Hmmm...the previous release was 128.50.3.1...
>
> I realize that the API portion advanced from 3.1 to 5.1, but the
> overall release number appears to be moving backwards. Is this
> intentional?
>
it is random and I also have no idea how it got generated. you are
right, the more important number is "5.1" which increase the API
version.
Thanks
Wey
On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
> Hi,
>
> Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
> Series
> WiFi Adapter is now available for download from
> http://intellinuxwireless.org/?n=Downloads
>
> Changes:
> - Fix "tid mismatch" issue
>
> Wey-Yi
Hmmm...the previous release was 128.50.3.1...
I realize that the API portion advanced from 3.1 to 5.1, but the
overall release number appears to be moving backwards. Is this
intentional?
John
--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.
On Wed, Apr 06, 2011 at 04:24:30PM +0200, Johannes Berg wrote:
> On Wed, 2011-04-06 at 10:12 -0400, John W. Linville wrote:
> > On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
> > > Hi,
> > >
> > > Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
> > > Series
> > > WiFi Adapter is now available for download from
> > > http://intellinuxwireless.org/?n=Downloads
> > >
> > > Changes:
> > > - Fix "tid mismatch" issue
> > >
> > > Wey-Yi
> >
> > Hmmm...the previous release was 128.50.3.1...
> >
> > I realize that the API portion advanced from 3.1 to 5.1, but the
> > overall release number appears to be moving backwards. Is this
> > intentional?
>
> They're all over the place and basically random ... I *think* they
> depend on the branch it comes from internally, but I'm not even sure.
OK, I can cope. But if you (i.e. your team) can influence them
towards a sane numbering scheme, it will probably make packagers
and/or release engineers happier in the distros...
John
--
John W. Linville Someday the world will need a hero, and you
[email protected] might be all we have. Be ready.