From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Chen-Yu Tsai <wens@csie.org>,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: sun8i: r40/v40: rewrite BPi M2 Berry DTS to rebase on M2 Ultra
Date: Thu, 26 Jul 2018 17:24:27 +0200 [thread overview]
Message-ID: <20180726152427.cjji4ymwfjifja4q@flea> (raw)
In-Reply-To: <BA51039A-02DD-42C2-A7A9-E1B866074CA6@aosc.io>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Thu, Jul 26, 2018 at 08:47:34PM +0800, Icenowy Zheng wrote:
>
>
> 于 2018年7月26日 GMT+08:00 下午8:41:19, Maxime Ripard <maxime.ripard@bootlin.com> 写到:
> >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,
> >
> >Do you have a reference for this?
>
> See [1], it says "BPI-M2U and BPI-M2 Berry share the same image".
>
> [1] http://www.banana-pi.org/download.html
Debian supports different SoC from different vendor using the same
image, so it's not really a good argument to share the device tree. I
mean, you can even boot an H3 to a shell using an A33 device tree.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-26 15:24 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
2018-07-26 12:41 ` Maxime Ripard
2018-07-26 12:47 ` Icenowy Zheng
2018-07-26 15:24 ` Maxime Ripard [this message]
2018-07-26 15:26 ` Icenowy Zheng
2018-08-08 10:36 ` [linux-sunxi] " Icenowy Zheng
2018-08-20 12:00 ` Maxime Ripard
2018-08-20 12:06 ` Icenowy Zheng
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=20180726152427.cjji4ymwfjifja4q@flea \
--to=maxime.ripard@bootlin.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=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