From: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Inochi Amaoto <inochiama@outlook.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] riscv: dts: sophgo: add initial Milk-V Duo S board support
Date: Tue, 23 Apr 2024 09:57:56 +0200 [thread overview]
Message-ID: <4b5657be-686b-460f-bc04-b023ffbe1910@bootlin.com> (raw)
In-Reply-To: <fbdcc77e-eab4-41da-803c-d65405f37f02@bootlin.com>
Hello Michael,
> By the way, where's the best source of information about the Sophgo
> sg2000 and sg2002 processors? Even the Sophgo website doesn't seem to
> have them :-/ . It just mentions the CV18xx ones.
The best source of information I found for the Sophgo SG2002 and SG200
is this Github repository from Sophgo :
https://github.com/sophgo/sophgo-doc
It contains the Technical Reference Manual for the Sophgo SG2000, SG2002
and SG2042.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-23 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 6:53 [PATCH v5 0/2] add initial Milk-V Duo S board support michael.opdenacker
2024-04-17 6:53 ` [PATCH v5 1/2] dt-bindings: riscv: add Milk-V Duo S board compatibles michael.opdenacker
2024-04-17 9:25 ` Inochi Amaoto
2024-04-17 6:53 ` [PATCH v5 2/2] riscv: dts: sophgo: add initial Milk-V Duo S board support michael.opdenacker
2024-04-17 9:34 ` Inochi Amaoto
2024-04-17 15:06 ` Conor Dooley
2024-04-17 22:29 ` Inochi Amaoto
2024-04-21 5:57 ` Michael Opdenacker
2024-04-21 6:30 ` Inochi Amaoto
2024-04-23 6:11 ` Michael Opdenacker
2024-04-23 7:57 ` Thomas Bonnefille [this message]
2024-04-23 8:24 ` Inochi Amaoto
2024-04-17 9:19 ` [PATCH v5 0/2] " Emil Renner Berthing
2024-04-21 5:58 ` Michael Opdenacker
2024-04-18 15:43 ` Rob Herring
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=4b5657be-686b-460f-bc04-b023ffbe1910@bootlin.com \
--to=thomas.bonnefille@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.opdenacker@bootlin.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox