From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2
Date: Tue, 9 May 2017 09:13:08 -0400 [thread overview]
Message-ID: <20170509131308.GR12511@bill-the-cat> (raw)
In-Reply-To: <20170509124341.GA5304@eris.local>
On Tue, May 09, 2017 at 02:43:41PM +0200, Patrick Wildt wrote:
> The NanoPi Neo2 is basically the same as the NanoPi Neo, but that they
> replaced the SoC with the 64-bit Allwinner H5 SoC. Add a (64-bit only)
> defconfig defining the required options to build the U-Boot proper.
>
> Create a new .dts file for it by including the (32-bit) H3 SoC .dtsi
> and changing the differing components accordingly, like it's been
> done for the OrangePi PC 2.
>
> Signed-off-by: Patrick Wildt <patrick@blueri.se>
> ---
> arch/arm/dts/Makefile | 1 +
> arch/arm/dts/sun50i-h5-nanopi-neo2.dts | 170 +++++++++++++++++++++++++++++++++
Is this dts file coming from the Linux Kernel? If so, please cite the
githash / tag that it's from, thanks.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170509/8337ec32/attachment.sig>
next prev parent reply other threads:[~2017-05-09 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 12:43 [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2 Patrick Wildt
2017-05-09 13:13 ` Tom Rini [this message]
2017-05-24 11:50 ` Andreas Färber
2017-05-24 12:44 ` Andre Przywara
2017-05-24 12:52 ` Tom Rini
2017-05-24 14:27 ` Andreas Färber
2017-06-01 12:45 ` Patrick Wildt
2017-06-01 12:57 ` Tom Rini
2017-06-01 14:04 ` Patrick Wildt
2017-06-01 14:53 ` Andreas Färber
2017-06-01 14:57 ` Jagan Teki
2017-06-01 15:56 ` Patrick Wildt
2017-06-01 15:57 ` Tom Rini
2017-06-01 15:59 ` Patrick Wildt
2017-06-01 16:03 ` Tom Rini
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=20170509131308.GR12511@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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