From: "Andreas Färber" <afaerber@suse.de>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Bizon <bizongod@gmail.com>,
"Andreas Färber" <afaerber@suse.de>,
meleservice@mele.cn, devicetree@vger.kernel.org
Subject: [PATCH 0/3] arm64: dts: Initial MeLE V9 support
Date: Mon, 16 Oct 2017 05:01:50 +0200 [thread overview]
Message-ID: <20171016030153.11078-1-afaerber@suse.de> (raw)
Hello,
This mini-series adds a Device Tree for the MeLE V9 Android Media Player.
Same as with PROBOX2 AVA, serial (loady) was the only working way to boot a new
kernel from the vendor's U-Boot on this TV box.
More details at:
https://en.opensuse.org/HCL:Mele_V9
@MeLE: Please review the following three patches and either signal your
acknowledgement of my naming proposals with an "Acked-by: name <email>"
response or point out any changes you would like to see applied. Thanks!
Latest experimental patches at:
https://github.com/afaerber/linux/commits/rtd1295-next
Have a lot of fun!
Cheers,
Andreas
Cc: meleservice@mele.cn
Cc: devicetree@vger.kernel.org
Andreas Färber (3):
dt-bindings: Add vendor prefix for MeLE
dt-bindings: arm: realtek: Document MeLE V9
arm64: dts: realtek: Add MeLE V9
Documentation/devicetree/bindings/arm/realtek.txt | 1 +
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm64/boot/dts/realtek/Makefile | 1 +
arch/arm64/boot/dts/realtek/rtd1295-mele-v9.dts | 31 ++++++++++++++++++++++
4 files changed, 34 insertions(+)
create mode 100644 arch/arm64/boot/dts/realtek/rtd1295-mele-v9.dts
--
2.13.6
next reply other threads:[~2017-10-16 3:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 3:01 Andreas Färber [this message]
2017-10-16 3:01 ` [PATCH 1/3] dt-bindings: Add vendor prefix for MeLE Andreas Färber
2017-10-23 22:37 ` Rob Herring
2017-10-16 3:01 ` [PATCH 2/3] dt-bindings: arm: realtek: Document MeLE V9 Andreas Färber
2017-10-23 22:37 ` Rob Herring
2017-10-16 3:01 ` [PATCH 3/3] arm64: dts: realtek: Add " Andreas Färber
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=20171016030153.11078-1-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=bizongod@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meleservice@mele.cn \
/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®