From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wifi: ath12k: enable WIPHY_FLAG_DISABLE_WEXT
Date: Mon, 15 Apr 2024 20:17:01 +0300 [thread overview]
Message-ID: <87cyqqy29e.fsf@kernel.org> (raw)
In-Reply-To: <c5080887-6d94-405d-a57b-dae5e6a57721@quicinc.com> (Jeff Johnson's message of "Mon, 15 Apr 2024 09:59:21 -0700")
Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> On 4/15/2024 9:27 AM, Kalle Valo wrote:
>> Jeff Johnson <quic_jjohnson@quicinc.com> writes:
>>> Is there a Ubuntu / Network Manager fix fir this?
>>
>> I would hope that Network Manager doesn't use WEXT or especially run the
>> iwconfig tool. This is why I suspect that you run iwconfig manually.
>
> I am not running iwconfig manually. I'm simply using the Ubuntu wifi settings
> menu to enable Hotspot. So somewhere under the hood Ubuntu/NM is running iwconfig
Oh man, screenscraping iwconfig is horrible. I would be very curious to
know what software exactly does this. This makes even more important to
extend the cfg80211 wext warning per process, otherwise there can be
more of these which are not detected.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-04-15 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 16:56 [PATCH] wifi: ath12k: enable WIPHY_FLAG_DISABLE_WEXT Kalle Valo
2024-04-11 19:41 ` Jeff Johnson
2024-04-11 20:59 ` Jeff Johnson
2024-04-13 19:15 ` Jeff Johnson
2024-04-15 16:27 ` Kalle Valo
2024-04-15 16:59 ` Jeff Johnson
2024-04-15 17:17 ` Kalle Valo [this message]
2024-04-18 15:21 ` Kalle Valo
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=87cyqqy29e.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.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