Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: "Marcel Weißenbach" <mweissenbach@ignaz.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: RTL8852BE wifi no longer working after 6.11 upgrade
Date: Tue, 24 Sep 2024 02:29:49 +0000	[thread overview]
Message-ID: <3784ba9d7af34d41b439b7ee0d9e9f8f@realtek.com> (raw)
In-Reply-To: 20240918114718.Horde.TpiB1MVH0uadLCQXUbR5WtB@ignaz.org

Ping-Ke Shih wrote:
> Marcel Weißenbach <mweissenbach@ignaz.org> wrote:
> > First of all, thank you so much for your time and work!
> >
> > I hope i don't cause any confusion and this question may be based on my lack of  understanding the patch,
> > i almost don't dare to ask, but does this quirk only gets into affect, when someone uses the same mainboard
> > i use? Is this an rather rare case that probably won't effect other people?
> >
> > I can't judge that so please don't get me wrong, but i feel a bit uneasy about this. I assume that most
> > fist time Linux users that have similar (but not the same) platform, where this quirk will not get applied
> > and they end up with non-working wifi, just notice that wifi doesn't work and give up on Linux and remember
> > it as "My Wifi even didn't work there".
> >
> > As a long time Gentoo user, i have the capability to build my own kernel and provide feedback that can
> help
> > fix this issue, but i assume most users don't. I would assume an Ubuntu users will just remove the Ubuntu
> > partition and calls it a day continuing using Windows. I am a bit worried and wonder, if there maybe a
> way
> > to fix that, that is independent on my specific hardware/mainboard.
> >
> > Of course, feel free to correct me if i am getting something wrong here, im neither an Kernel nor C expert
> > and thank you for your time again.
> >
> 
> You are right. I was not aware of that. I will discuss people internally and reconsider the solution.

With internal discussion, the early chips including RTL8852BE have interoperability
problem with some platforms, so we decide to rollback to 32-bit DMA for these chips,
and only enable 36-bit DMA for tested platforms. 

Please help to test if [1] works to you. 

[1] https://lore.kernel.org/linux-wireless/20240924021633.19861-1-pkshih@realtek.com/T/#u


  parent reply	other threads:[~2024-09-24  2:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17  5:57 RTL8852BE wifi no longer working after 6.11 upgrade Marcel Weißenbach
2024-09-18  6:02 ` Ping-Ke Shih
2024-09-18  7:32   ` Marcel Weißenbach
2024-09-18  9:00     ` Ping-Ke Shih
2024-09-18 11:47       ` Marcel Weißenbach
2024-09-19  0:21         ` Ping-Ke Shih
2024-09-24  2:29         ` Ping-Ke Shih [this message]
2024-09-27  1:20           ` Marcel Weißenbach

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=3784ba9d7af34d41b439b7ee0d9e9f8f@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mweissenbach@ignaz.org \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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