U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2
Date: Wed, 24 May 2017 08:52:04 -0400	[thread overview]
Message-ID: <20170524125204.GC18884@bill-the-cat> (raw)
In-Reply-To: <b3772783-fa97-b59a-cc6a-ed614af99f12@arm.com>

On Wed, May 24, 2017 at 01:44:26PM +0100, Andre Przywara wrote:
> Hi,
> 
> On 24/05/17 12:50, Andreas Färber wrote:
> > Hej Patrick,
> > 
> > Am 09.05.2017 um 14:43 schrieb Patrick Wildt:
> >> 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>
> > 
> > I've tested this patch on top of yesterday's master branch
> > (4c78028737c3185f49f5691183aeac3478b5f699 "mksunxi_fit_atf.sh: Allow for
> > this to complete when bl31.bin is missing").
> > 
> > Considering Tom's unanswered question, is there any diff to the upstream
> > kernel .dts? Expected would be to just copy the Linux .dts file here and
> > to state which tree and commit/tag it was taken from.
> 
> I think we have a similar diversion between Linux and U-Boot .dts here,
> given that the U-Boot support was merged earlier.
> Updating the DTs for H5 and the board(s) was on my plan, but it's a bit
> more involved since it affects the H3 .dts as well (H3 and H5 use a
> shared stub .dtsi now). Also the H5 .dtsi just got into Linux
> (4.12-rc1), so it hasn't been in an officially released kernel yet.

I'm fine with re-syncing to v4.12-rc2, btw.

-- 
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/20170524/89bd152d/attachment.sig>

  reply	other threads:[~2017-05-24 12:52 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
2017-05-24 11:50 ` Andreas Färber
2017-05-24 12:44   ` Andre Przywara
2017-05-24 12:52     ` Tom Rini [this message]
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=20170524125204.GC18884@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