From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 3/3] ARM: dts: sun8i-h3: Add dts file for Sinovoip BPI-M2+
Date: Tue, 7 Jun 2016 22:44:26 +0200 [thread overview]
Message-ID: <20160607204426.GB14179@lukather> (raw)
In-Reply-To: <1464853811-15233-4-git-send-email-wens@csie.org>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Thu, Jun 02, 2016 at 03:50:11PM +0800, Chen-Yu Tsai wrote:
> The BPI-M2+ is an H3 development board. It is a smaller form factor than
> the original BPI-M2, with the new H3 SoC.
>
> It has 1GB DRAM, 8GB eMMC, a micro SD card slot, HDMI output, 2 USB
> host connector and 1 USB OTG connector, an IR receiver, WiFi+BT based
> on Ampak AP6212.
>
> The board also has a 3 pin header for (debug) UART, a 40 pin GPIO header
> based on the Raspberry Pi B+, but the peripheral signals are not the
> same, and an FPC connector for connecting BPI's camera.
>
> Signed-off-by: Chen-Yu Tsai <wens@csie.org>
I fixed the whitespace error, and applied all three.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-06-07 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 7:50 [PATCH 0/3] ARM: dts: sun8i-h3: Add dts file for Sinovoip BPI-M2+ Chen-Yu Tsai
2016-06-02 7:50 ` [PATCH 1/3] ARM: dts: sun8i-h3: move uart0 pins to sort pinmux list in proper order Chen-Yu Tsai
2016-06-02 7:50 ` [PATCH 2/3] ARM: dts: sun8i-h3: Add uart1 pinmux setting Chen-Yu Tsai
2016-06-02 7:50 ` [PATCH 3/3] ARM: dts: sun8i-h3: Add dts file for Sinovoip BPI-M2+ Chen-Yu Tsai
2016-06-07 20:44 ` Maxime Ripard [this message]
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=20160607204426.GB14179@lukather \
--to=maxime.ripard@free-electrons.com \
--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;
as well as URLs for NNTP newsgroup(s).