From: Zhang Ning <zhangn1985@outlook.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
nick@khadas.com
Cc: linux-amlogic@lists.infradead.org
Subject: Re: VIM1's wifi doesn't work after update to Linux 6.1
Date: Fri, 9 Dec 2022 08:45:20 +0800 [thread overview]
Message-ID: <OS0P286MB06415F3F763BEDC6870313A8CD1C9@OS0P286MB0641.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Y5KAxhvFzvoNYL2j@orangepipc>
I find a issue in linux-wireless:
https://www.spinics.net/lists/linux-wireless/msg229742.html
same timeout, but it says brcm firmware crash.
but I don't see any firmware crash log, (I don't know whether crash log
would goto linux console)
@Nick, do you have time to try this issue in your side, and is it
possible to ask your supplier for newer firmware?
BR.
Ning.
On Fri, Dec 09, 2022 at 08:26:51AM +0800, Zhang Ning wrote:
> On Thu, Dec 08, 2022 at 10:40:26PM +0100, Martin Blumenstingl wrote:
> > Hello Ning,
> >
> > On Thu, Dec 8, 2022 at 2:02 PM Zhang Ning <zhangn1985@outlook.com> wrote:
> > > After update khadas VIM1's kernel to 6.1-rc7, WIFI stop working, with
> > > below log:
> > [...]
> > That's unfortunate. Have you tried reverting commit 066ecde6d826b4
> > "mmc: meson-gx: add SDIO interrupt support"? I'm not saying that
> > reverting that patch is the correct way to fix this issue. It's one of
> > the few recent driver changes though, so at least it's a starting
> > point.
> >
> > > I applied "WIP-arm64-dts-meson-set-p212-p23x-q20x-SDIO-to-100MH.patch"
> > > to VIM1's kernel 6.1.0-rc7, is it related?
> > Have you tried without that patch as well?
>
> I have tried revert 066ecde6d826b4, and remove SDIO-to-100MH.patch,
> rebuild meson_gx_mmc and dtb, replace original, this issue still
> happens.
>
> BR.
> Ning.
> >
> >
> > Best regards,
> > Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2022-12-09 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 13:02 Zhang Ning
2022-12-08 21:40 ` Martin Blumenstingl
2022-12-08 23:32 ` Zhang Ning
2022-12-09 0:26 ` Zhang Ning
[not found] ` <Y5KAxhvFzvoNYL2j@orangepipc>
2022-12-09 0:45 ` Zhang Ning [this message]
2022-12-18 2:00 ` Zhang Ning
2022-12-25 1:14 ` Update: " Zhang Ning
2022-12-25 2:42 ` Zhang Ning
2022-12-09 10:57 Christian Hewitt
2022-12-12 12:57 ` Zhang Ning
2022-12-12 13:41 ` Christian Hewitt
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=OS0P286MB06415F3F763BEDC6870313A8CD1C9@OS0P286MB0641.JPNP286.PROD.OUTLOOK.COM \
--to=zhangn1985@outlook.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=nick@khadas.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
all inboxes | Powered by JetHome®