From: Simon Baatz <gmbnomis@gmail.com>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, linux-sunxi@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: sun8i: r40/v40: rewrite BPi M2 Berry DTS to rebase on M2 Ultra
Date: Tue, 24 Jul 2018 20:36:15 +0200 [thread overview]
Message-ID: <20180724183613.GA10380@gandalf> (raw)
In-Reply-To: <20180724163655.61365-1-icenowy@aosc.io>
On Wed, Jul 25, 2018 at 12:36:55AM +0800, Icenowy Zheng wrote:
> Banana Pi designs the BPi M2 Berry board to be software compatible with
> BPi M2 Ultra, so it's based on M2 Ultra with some function cuts,
> including:
>
> - 2048MiB DRAM -> 1024MiB (this should be proceed by the bootloader);
> - dropped a LED;
> - dropped eMMC;
> - dropped USB2 and connect USB1 to a 4-port HUB.
>
> Thus we can make the M2 Berry device tree based on the M2 Ultra, rather
> than write one from scratch.
Good idea! I know that Ultra came first and then the cut-down Berry.
But from a device tree point of view, wouldn't it make more sense to
take M2 Berry as the base and just add the hardware for M2 Ultra?
next prev parent reply other threads:[~2018-07-24 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 16:36 [PATCH] ARM: dts: sun8i: r40/v40: rewrite BPi M2 Berry DTS to rebase on M2 Ultra Icenowy Zheng
2018-07-24 18:36 ` Simon Baatz [this message]
[not found] ` <20180724163655.61365-1-icenowy-h8G6r0blFSE@public.gmane.org>
2018-07-26 12:41 ` Maxime Ripard
2018-07-26 12:47 ` Icenowy Zheng
[not found] ` <BA51039A-02DD-42C2-A7A9-E1B866074CA6-h8G6r0blFSE@public.gmane.org>
2018-07-26 15:24 ` Maxime Ripard
2018-07-26 15:26 ` Icenowy Zheng
2018-08-08 10:36 ` [linux-sunxi] " Icenowy Zheng
[not found] ` <dc8a28bcfbe082158bac5b097badb3ddf0f51ce8.camel-h8G6r0blFSE@public.gmane.org>
2018-08-20 12:00 ` Maxime Ripard
2018-08-20 12:06 ` Icenowy Zheng
[not found] ` <2782CDF6-C36F-49EF-97AE-75382C416489-h8G6r0blFSE@public.gmane.org>
2018-08-20 15:02 ` Maxime Ripard
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=20180724183613.GA10380@gandalf \
--to=gmbnomis@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@bootlin.com \
--cc=wens@csie.org \
/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;
as well as URLs for NNTP newsgroup(s).