From: "Sandie Cao" <sandie.cao@deepcomputing.io>
To: "Emil Renner Berthing" <kernel@esmil.dk>
Cc: "Conor Dooley" <conor@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Heiko Stuebner" <heiko.stuebner@cherry.de>,
"Neil Armstrong" <neil.armstrong@linaro.org>, <rafal@milecki.pl>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Michael Zhu" <michael.zhu@starfivetech.com>,
"Drew Fustini" <drew@beagleboard.org>,
<linux-riscv@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <dhs@frame.work>,
<ams@frame.work>, <gregkh@linuxfoundation.org>,
<yuning.liang@deepcomputing.io>, <huiming.qiu@deepcomputing.io>,
"Sandie Cao" <sandie.cao@deepcomputing.io>
Subject: [PATCH v3 0/3] Add Framework FRANME0000 dts
Date: Wed, 25 Sep 2024 13:31:20 +0800 [thread overview]
Message-ID: <20240925053123.1364574-1-sandie.cao@deepcomputing.io> (raw)
DeepComputing is creating a RISC-V Framework Laptop 13 Mainboard
powered by a StarFive JH7110 processor.This is a developer-focused
product, aimed at making tinkering with RISC-V more accessible.
The Mainboard is under development and we'll share more on functionality,
compatibility, and availability as the program progresses.
Framework Model: Framework FRANME0000
DeepComputing Model: DeepComputing fm7110
V1:
- Add framework dts and config.
V2:
- Add deepcomputing into vendor list.
- Add deepcomputing,fm7110 into model compatible list.
- Fix the error about dtbs_check.
- Framework Config will be included in later patch.
V3:
- Update board features into description
Sandie Cao (3):
dt-bindings: vendor: add deepcomputing
dt-bindings: riscv: starfive: add deepcomputing,fm7110
riscv: dts: starfive: add framework dts
.../devicetree/bindings/riscv/starfive.yaml | 1 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 ++
arch/riscv/boot/dts/starfive/Makefile | 1 +
.../boot/dts/starfive/jh7110-framework.dts | 34 +++++++++++++++++++
4 files changed, 38 insertions(+)
create mode 100644 arch/riscv/boot/dts/starfive/jh7110-framework.dts
base-commit: abf2050f51fdca0fd146388f83cddd95a57a008d
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2024-09-25 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 5:31 Sandie Cao [this message]
2024-09-25 7:31 ` [PATCH v3 0/3] Add Framework FRANME0000 dts Krzysztof Kozlowski
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=20240925053123.1364574-1-sandie.cao@deepcomputing.io \
--to=sandie.cao@deepcomputing.io \
--cc=ams@frame.work \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dhs@frame.work \
--cc=drew@beagleboard.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.stuebner@cherry.de \
--cc=huiming.qiu@deepcomputing.io \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.zhu@starfivetech.com \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=yuning.liang@deepcomputing.io \
/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