From: Ping-Ke Shih <pkshih@realtek.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Savyasaachi Vanga <savyasaachiv@gmail.com>,
Christian Heusel <christian@heusel.eu>
Cc: Kalle Valo <kvalo@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: RE: [REGRESSION][BISECTED] wifi: RTL8821CE does not work in monitor mode
Date: Wed, 12 Jun 2024 08:43:09 +0000 [thread overview]
Message-ID: <3dd46abad6f8485fa74d36278dda46ac@realtek.com> (raw)
In-Reply-To: <7869b9b29b6796c95fd5af649e4bd6696e56dcaf.camel@sipsolutions.net>
Johannes Berg <johannes@sipsolutions.net>
> On Wed, 2024-06-12 at 09:07 +0200, Johannes Berg wrote:
> > On Wed, 2024-06-12 at 00:56 +0000, Ping-Ke Shih wrote:
> >
> >
> > > > Just got pinged (sp?) about this, can you share the driver fix so I can
> > > > take a look what the issue is about?
> > > >
> > >
> > > Please reference patch below. I copy this idea from rtw89 [1], which the main
> > > stuff is to add WANT_MONITOR_VIF and case NL80211_IFTYPE_MONITOR in add_interface().
> >
> > Ah, OK, but that gives me a hint. Yes, I see the issue now.
> >
> > OK it's not trivial and it might leave ath12k still not working (though
> > not sure it ever did before? or maybe I'm missing something...), but I
> > think I can fix this. Let's see.
> >
>
> I don't have any of the affected hardware, could someone test this?
>
> https://p.sipsolutions.net/619a4ce4a197b2b4.txt
>
Tested on 6.9.2 with RTL8822CE.
Before this patch, it can capture packets but always stays on channel 1.
With this patch, I switch channel 1 --> 36 --> 149 --> 11.
All are expected.
Thanks for the quick fix!
Ping-Ke
next prev parent reply other threads:[~2024-06-12 8:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 22:01 [REGRESSION][BISECTED] wifi: RTL8821CE does not work in monitor mode Christian Heusel
2024-05-28 5:22 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-28 11:50 ` Christian Heusel
2024-05-28 8:21 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-31 5:58 ` Thorsten Leemhuis
2024-06-03 0:47 ` Ping-Ke Shih
2024-06-11 15:25 ` Johannes Berg
2024-06-12 0:56 ` Ping-Ke Shih
2024-06-12 7:07 ` Johannes Berg
2024-06-12 7:58 ` Johannes Berg
2024-06-12 8:43 ` Ping-Ke Shih [this message]
2024-06-12 8:45 ` Johannes Berg
2024-06-12 8:49 ` Ping-Ke Shih
2024-06-12 13:31 ` Christian Heusel
2024-06-12 9:12 ` Vasanthakumar Thiagarajan
2024-06-06 13:36 ` Thorsten Leemhuis
2024-06-12 10:23 ` [PATCH] wifi: mac80211: fix monitor channel with chanctx emulation Johannes Berg
2024-06-16 22:02 ` Christian Heusel
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=3dd46abad6f8485fa74d36278dda46ac@realtek.com \
--to=pkshih@realtek.com \
--cc=christian@heusel.eu \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=savyasaachiv@gmail.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