From: Joshua Milas <josh.milas@gmail.com>
To: Shuwei Wu <shuwei.wu@mailbox.org>
Cc: tglx@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, pjw@kernel.org, samuel.holland@sifive.com,
unicorn_wang@outlook.com, inochiama@gmail.com,
daniel.lezcano@linaro.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
liujingqi@lanxincomputing.com, alexander.sverdlin@gmail.com,
rabenda.cn@gmail.com, dlan@kernel.org, chao.wei@sophgo.com,
anup@brainfault.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
sophgo@lists.linux.dev, hanguidong02@gmail.com,
michael.opdenacker@rootcommit.com,
linux-riscv <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [PATCH v5 RESEND 5/5] riscv64: dts: sophgo: add initial Milk-V Duo S board support
Date: Mon, 8 Jun 2026 08:06:17 -0400 [thread overview]
Message-ID: <aiawOUHBcKtMVEZk@sleek> (raw)
In-Reply-To: <DJ0ZYF5C8MMH.2GBBY188VVPSH@mailbox.org>
Hi Shuwei,
Thanks for testing! I am seeing the same wifi issue on my end and have been
looking into it so it may not be a config issue.
I was able to get the chip enumerated by adding some properties to the sdhci1
node and adding some quirks to the kernel source on reset. I was also not able
to get the chip powered without manually toggling PORTA pin 15 in code. Then I
tried using the aic8800 1.0.9 dkms module however it needs some changes because
it is not updated for Linux 7.1. I did find some Milk-V Duo S AIC8800 drivers
and will give it a shot soon.
Thanks again,
- Joshua Milas
WARNING: multiple messages have this Message-ID (diff)
From: Joshua Milas <josh.milas@gmail.com>
To: Shuwei Wu <shuwei.wu@mailbox.org>
Cc: tglx@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, pjw@kernel.org, samuel.holland@sifive.com,
unicorn_wang@outlook.com, inochiama@gmail.com,
daniel.lezcano@linaro.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr,
liujingqi@lanxincomputing.com, alexander.sverdlin@gmail.com,
rabenda.cn@gmail.com, dlan@kernel.org, chao.wei@sophgo.com,
anup@brainfault.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
sophgo@lists.linux.dev, hanguidong02@gmail.com,
michael.opdenacker@rootcommit.com,
linux-riscv <linux-riscv-bounces@lists.infradead.org>
Subject: Re: [PATCH v5 RESEND 5/5] riscv64: dts: sophgo: add initial Milk-V Duo S board support
Date: Mon, 8 Jun 2026 08:06:17 -0400 [thread overview]
Message-ID: <aiawOUHBcKtMVEZk@sleek> (raw)
In-Reply-To: <DJ0ZYF5C8MMH.2GBBY188VVPSH@mailbox.org>
Hi Shuwei,
Thanks for testing! I am seeing the same wifi issue on my end and have been
looking into it so it may not be a config issue.
I was able to get the chip enumerated by adding some properties to the sdhci1
node and adding some quirks to the kernel source on reset. I was also not able
to get the chip powered without manually toggling PORTA pin 15 in code. Then I
tried using the aic8800 1.0.9 dkms module however it needs some changes because
it is not updated for Linux 7.1. I did find some Milk-V Duo S AIC8800 drivers
and will give it a shot soon.
Thanks again,
- Joshua Milas
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-06-08 12:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 17:33 [PATCH v5 RESEND 0/5] Add initial Milk-V Duo S board support Joshua Milas
2026-05-30 17:33 ` Joshua Milas
2026-05-30 17:33 ` [PATCH v5 RESEND 1/5] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2026-05-30 17:33 ` Joshua Milas
2026-05-31 12:29 ` Krzysztof Kozlowski
2026-05-31 12:29 ` Krzysztof Kozlowski
2026-05-30 17:33 ` [PATCH v5 RESEND 2/5] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2026-05-30 17:33 ` Joshua Milas
2026-05-30 17:46 ` sashiko-bot
2026-05-30 22:01 ` Inochi Amaoto
2026-05-30 22:01 ` Inochi Amaoto
2026-05-30 17:33 ` [PATCH v5 RESEND 3/5] dt-bindings: soc: sophgo: add sg2000 plic and clint documentation Joshua Milas
2026-05-30 17:33 ` Joshua Milas
2026-05-31 12:30 ` Krzysztof Kozlowski
2026-05-31 12:30 ` Krzysztof Kozlowski
2026-05-30 17:33 ` [PATCH v5 RESEND 4/5] riscv64: dts: sophgo: add SG2000 dtsi Joshua Milas
2026-05-30 17:33 ` Joshua Milas
2026-05-30 17:56 ` sashiko-bot
2026-06-05 9:33 ` Shuwei Wu
2026-06-05 9:33 ` Shuwei Wu
2026-06-08 12:06 ` Joshua Milas
2026-06-08 12:06 ` Joshua Milas
2026-05-30 17:33 ` [PATCH v5 RESEND 5/5] riscv64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2026-05-30 17:33 ` Joshua Milas
2026-05-30 18:02 ` sashiko-bot
2026-05-30 22:00 ` Inochi Amaoto
2026-05-30 22:00 ` Inochi Amaoto
2026-06-05 9:09 ` Shuwei Wu
2026-06-05 9:09 ` Shuwei Wu
2026-06-08 12:06 ` Joshua Milas [this message]
2026-06-08 12:06 ` Joshua Milas
2026-05-30 22:02 ` [PATCH v5 RESEND 0/5] Add " Inochi Amaoto
2026-05-30 22:02 ` Inochi Amaoto
2026-06-08 13:28 ` Joshua Milas
2026-06-08 13:28 ` Joshua Milas
2026-06-02 8:19 ` (subset) " Inochi Amaoto
2026-06-02 8:19 ` Inochi Amaoto
2026-06-02 8:22 ` Inochi Amaoto
2026-06-02 8:22 ` Inochi Amaoto
2026-06-02 8:26 ` Inochi Amaoto
2026-06-02 8:26 ` Inochi Amaoto
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=aiawOUHBcKtMVEZk@sleek \
--to=josh.milas@gmail.com \
--cc=alex@ghiti.fr \
--cc=alexander.sverdlin@gmail.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=hanguidong02@gmail.com \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv-bounces@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liujingqi@lanxincomputing.com \
--cc=michael.opdenacker@rootcommit.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=shuwei.wu@mailbox.org \
--cc=sophgo@lists.linux.dev \
--cc=tglx@kernel.org \
--cc=unicorn_wang@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.