From: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Peter Chen <peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org
Subject: Re: [PATCH v2 0/2] ARM: imx6sx-sdb: add revb board
Date: Thu, 26 Feb 2015 15:58:41 +0800 [thread overview]
Message-ID: <20150226075838.GF20028@dragon> (raw)
In-Reply-To: <1421804094-26379-1-git-send-email-peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
On Wed, Jan 21, 2015 at 09:34:52AM +0800, Peter Chen wrote:
> Hi Shawn,
>
> The imx6sx-sdb board has two revisions, the current mainline is the
> reva which is experimental and will not be released, the revb board
> is used widely for internal and external users.
>
> The main changes between reva and revb board:
> - OOP setting
> - pfuse
> - qspi
> - can transceiver (not mainlined)
>
> Changes for v2:
>
> - Add missing Makefile entries for both dts files. [Patch 1/2] and [Patch 2/2]
> - Delete OOP setting changed at imx6sx-sdb-reva, it is SoC feature,
> it doesn't need to be change unless board limitations. [Patch 1/2]
> - Add explanation why OOP setting need to changed at imx6sx-sdb revb board. [Patch 2/2]
> - Make imx6sx-sdb revb board as default imx6sx-sdb board. [Patch 2/2]
>
> Peter Chen (2):
> ARM: imx6sx-sdb: change default board as reva board
> ARM: imx6sx-sdb: add revb board and make it default
Peter,
What branch did you generate these patches on? I'm trying to apply
them, but they do not apply on any reasonable branch. Can you re-spin
against v4.0-rc1? Thanks.
Shawn
>
> arch/arm/boot/dts/Makefile | 3 +-
> arch/arm/boot/dts/imx6sx-sdb-reva.dts | 143 +++++++++
> arch/arm/boot/dts/imx6sx-sdb.dts | 588 ++--------------------------------
> arch/arm/boot/dts/imx6sx-sdb.dtsi | 547 +++++++++++++++++++++++++++++++
> 4 files changed, 720 insertions(+), 561 deletions(-)
> create mode 100644 arch/arm/boot/dts/imx6sx-sdb-reva.dts
> create mode 100644 arch/arm/boot/dts/imx6sx-sdb.dtsi
>
> --
> 1.9.1
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-26 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 1:34 [PATCH v2 0/2] ARM: imx6sx-sdb: add revb board Peter Chen
[not found] ` <1421804094-26379-1-git-send-email-peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-01-21 1:34 ` [PATCH v2 1/2] ARM: imx6sx-sdb: change default board as reva board Peter Chen
2015-01-21 1:34 ` [PATCH v2 2/2] ARM: imx6sx-sdb: add revb board and make it default Peter Chen
2015-02-26 7:58 ` Shawn Guo [this message]
2015-02-26 9:18 ` [PATCH v2 0/2] ARM: imx6sx-sdb: add revb board Peter Chen
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=20150226075838.GF20028@dragon \
--to=shawn.guo-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pawel.moll-5wv7dgnIgG8@public.gmane.org \
--cc=peter.chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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