From: Zhang Ning <zhangn1985@outlook.com>
To: linux-amlogic@lists.infradead.org
Cc: martin.blumenstingl@googlemail.com, nick@khadas.com
Subject: Re: Update: Re: VIM1's wifi doesn't work after update to Linux 6.1
Date: Sun, 25 Dec 2022 10:42:53 +0800 [thread overview]
Message-ID: <OS0P286MB06412371C5E6FE4DFDEC1DB1CDEF9@OS0P286MB0641.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <OS0P286MB06414BA3239D9BE69DA18E0CCDEF9@OS0P286MB0641.JPNP286.PROD.OUTLOOK.COM>
On Sun, Dec 25, 2022 at 09:14:56AM +0800, Zhang Ning wrote:
> Hi, All
>
> In previous emails, I heard WIFI works fine.
>
> I asked Nick for their tree for linux-6.1.
> (due to their tree have some package patches, which make fail to build
> deb, I picked other patches)
> here is my tree: https://github.com/zhangn1985/linux-stable.git
bisected: "mmc: meson-gx: add SDIO interrupt support", which is pointed
out by Martin, I don't know why I'm wrong in first try.
>
> I build it in an arm64 chroot env (faster than real arm64 board), with below commands:
> ```
> make kvims_defconfig
> make bindeb-pkg -j`nproc`
> ```
>
> install to my VIM1, connect it to WIFI router and run:
> ```
> while true; do curl www.baidu.com; done
> ```
>
> it stucks after 3mins, same logs shown in previous email.
>
> here is my brcm firmware md5:
> 501ca4e8307ad8e71c32f0d24369bada brcmfmac43455-sdio.bin
> d3ad92472ef030c3897062ff809a9083 brcmfmac43455-sdio.txt
>
> BR.
> Ning.
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-12-25 3:21 UTC|newest]
Thread overview: 8+ 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
2022-12-18 2:00 ` Zhang Ning
2022-12-25 1:14 ` Update: " Zhang Ning
2022-12-25 2:42 ` Zhang Ning [this message]
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=OS0P286MB06412371C5E6FE4DFDEC1DB1CDEF9@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®