From: Thomas Backlund <tmb@mageia.org>
To: Takashi Iwai <tiwai@suse.de>, Luca Coelho <luca@coelho.fi>
Cc: <dor.shaish@intel.com>, Josh Boyer <jwboyer@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
<linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Regression with the latest iwlwifi-9260-*-46.ucode
Date: Fri, 9 Aug 2019 22:00:15 +0300 [thread overview]
Message-ID: <1736104d-3ef4-83d1-2672-00f36b922ef7@mageia.org> (raw)
In-Reply-To: <s5ho912momt.wl-tiwai@suse.de>
Den 06-08-2019 kl. 16:04, skrev Takashi Iwai:
> On Mon, 05 Aug 2019 14:03:55 +0200,
> Now we got a feedback from the latest linux-firmware (20190726) and
> surprising the result was negative. The dmesg after the cold boot is
> found at:
> https://bugzilla.suse.com/show_bug.cgi?id=1142128#c26
>
> The kernel is 5.2.3, so it should be new enough.
>
> If anything else needed (or something missing), let us know.
>
I read on some forum that some commented that the "Add support for SAR
South Korea limitation" fix is needed, but it seemed weird...
Anyway, with theese on top of 5.2.7
39bd984c203e86f3 iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version
< 41
f5a47fae6aa3eb06 iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT
support
0c3d7282233c7b02 iwlwifi: Add support for SAR South Korea limitation
We have confirmation from an affected user that its now stable with both
older and newer firmwares...
And we earlier tried with only the:
39bd984c203e86f3 iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version
< 41
But that did not help (not that I really expected it since its loading
version 46 firmwares anyway)
So my guess is that the newer firmware actually subtly expects to get
the behaviour of the:
0c3d7282233c7b02 iwlwifi: Add support for SAR South Korea limitation
Of course that's still guessing and I assume only Intel fw guys can
verify that...
--
Thomas
next prev parent reply other threads:[~2019-08-09 19:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 15:35 Regression with the latest iwlwifi-9260-*-46.ucode Takashi Iwai
2019-07-19 16:36 ` Luciano Coelho
2019-07-19 18:07 ` Takashi Iwai
2019-07-20 20:42 ` Takashi Iwai
2019-07-20 20:49 ` Luca Coelho
2019-07-21 16:43 ` Takashi Iwai
2019-07-22 23:24 ` Brandon Darbro
2019-07-25 21:20 ` Brandon Darbro
2019-08-05 9:48 ` Luca Coelho
2019-08-05 9:53 ` Luca Coelho
2019-08-05 10:05 ` Takashi Iwai
2019-08-05 10:10 ` Luca Coelho
2019-08-05 12:03 ` Luca Coelho
2019-08-06 13:04 ` Takashi Iwai
2019-08-09 19:00 ` Thomas Backlund [this message]
2019-08-20 13:11 ` Luca Coelho
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=1736104d-3ef4-83d1-2672-00f36b922ef7@mageia.org \
--to=tmb@mageia.org \
--cc=dor.shaish@intel.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=jwboyer@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=tiwai@suse.de \
/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).