From: anoduck <anoduck@protonmail.com>
To: u-boot@lists.denx.de
Cc: Tom Rini <trini@konsulko.com>, Sumit Garg <sumit.garg@kernel.org>,
Minda Chen <minda.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
anoduck <anoduck@protonmail.com>,
The Anoduck <anoduck@protonmail.co>
Subject: [PATCH RFC PineTab-V DTS File v2 0/2] Pine64 Pinetab-V Device Tree Support
Date: Sun, 19 Jul 2026 22:02:16 +0000 [thread overview]
Message-ID: <20260719-develop-v2-0-91fdc4cd60a2@protonmail.com> (raw)
Provide support for the Pine64 Pinetab-V Risc-V 64bit Tablet
Signed-off-by: anoduck <anoduck@protonmail.com>
---
Changes in v2:
- Device Tree split into two separate files per request.
-- File 1: Previous Community Additions
-- File 2: Addition of support for sd card and EMMC
- Location corrected to `arch/riscv/dta`.
- Link to v1: https://lore.kernel.org/r/20260718-develop-v1-1-d4b5c0675f87@protonmail.com
---
anoduck (2):
RFC: Pine64 Pinetab-V dts Device Tree File
RFC: Pine64 Pinetab-V Device Tree File
arch/riscv/dts/jh7110-pine64-pinetabv-u-boot.dtsi | 1756 ++++++++++++++++++++
.../riscv/dts}/jh7110-pine64-pinetabv.dts | 7 +-
.../jh7110-starfive-visionfive-2-pinetab-v.dts | 12 -
3 files changed, 1760 insertions(+), 15 deletions(-)
---
base-commit: a83903122b85e34cf3ef1050bdfaa7b258f17b74
change-id: 20260718-develop-1e9fbc9b4fe0
Best regards,
--
anoduck <anoduck@protonmail.com>
next reply other threads:[~2026-07-19 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 22:02 anoduck [this message]
2026-07-19 22:02 ` [PATCH RFC PineTab-V DTS File v2 1/2] RFC: Pine64 Pinetab-V dts Device Tree File anoduck
2026-07-19 22:02 ` [PATCH RFC PineTab-V DTS File v2 2/2] RFC: Pine64 Pinetab-V " anoduck
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=20260719-develop-v2-0-91fdc4cd60a2@protonmail.com \
--to=anoduck@protonmail.com \
--cc=anoduck@protonmail.co \
--cc=hal.feng@starfivetech.com \
--cc=minda.chen@starfivetech.com \
--cc=rick@andestech.com \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.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