From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [linux-sunxi] Re: [PATCH] ARM: dts: sun8i: r40/v40: rewrite BPi M2 Berry DTS to rebase on M2 Ultra
Date: Mon, 20 Aug 2018 14:00:46 +0200 [thread overview]
Message-ID: <20180820120046.7tonxtb52q43ocfq@flea> (raw)
In-Reply-To: <dc8a28bcfbe082158bac5b097badb3ddf0f51ce8.camel@aosc.io>
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Hi!
On Wed, Aug 08, 2018 at 06:36:56PM +0800, Icenowy Zheng wrote:
> 在 2018-07-26四的 14:41 +0200,Maxime Ripard写道:
> > 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?
> >
> > > 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.
> >
> > Is it the exhaustive list?
>
> I have asked Mikey from Sinovoip, and he has agreed this.
>
> Here's a list provided by him, which covers some things I forgot:
> - 2GiB -> 1GiB
> - no eMMC
> - no onboard microphone
> - no IR
> - no charging (and power jack to USB)
> - USB change
> - one less LED
>
> Should I add this to the device tree's comment?
Not really, because...
> >
> > I'm a bit reluctant to merge that kind of patches usually, since that
> > would also imply that each time someone will commit something to the
> > M2-Ultra, it would automatically apply to the M2-Berry, without any
> > easy way to tell and / or test.
... this still applies.
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-08-20 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 16:36 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
2018-07-26 15:26 ` Icenowy Zheng
2018-08-08 10:36 ` [linux-sunxi] " Icenowy Zheng
2018-08-20 12:00 ` Maxime Ripard [this message]
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=20180820120046.7tonxtb52q43ocfq@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
Powered by JetHome