From: Andrew Morton <akpm@linux-foundation.org>
To: York Sun <yorksun@freescale.com>
Cc: timur@freescale.com, linux-fbdev-devel@lists.sourceforge.net,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, scottwood@freescale.com,
yorksun@freescale.com
Subject: Re: [PATCH 2/2 v5] Add DIU platform code for MPC8610HPCD
Date: Tue, 1 Apr 2008 14:00:29 -0700 [thread overview]
Message-ID: <20080401140029.be918d87.akpm@linux-foundation.org> (raw)
In-Reply-To: <12069806051291-git-send-email-yorksun@freescale.com>
On Mon, 31 Mar 2008 11:23:25 -0500
York Sun <yorksun@freescale.com> wrote:
> Add platform code to support Freescale DIU. The platform code includes
> framebuffer memory allocation, pixel format, monitor port, etc.
>
> Signed-off-by: York Sun <yorksun@freescale.com>
> Signed-off-by: Timur Tabi <timur@freescale.com>
> ---
> This patch addes platform support for Freescale DIU driver, targeting 2.6.26 kernel.
>
> arch/powerpc/configs/mpc8610_hpcd_defconfig | 198 +++++++++++++++++++++++----
> arch/powerpc/platforms/86xx/mpc8610_hpcd.c | 190 ++++++++++++++++++++++++--
> arch/powerpc/sysdev/fsl_soc.c | 41 ++++++
> arch/powerpc/sysdev/fsl_soc.h | 23 +++
> 4 files changed, 413 insertions(+), 39 deletions(-)
The defconfig change gets almost 100% rejects and probably isn't
appropriate here and isn't very important. I dropped that part of the
patch.
next prev parent reply other threads:[~2008-04-01 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 16:23 v5 patch to add FSL DIU framebuffer driver York Sun
2008-03-31 16:23 ` [PATCH 1/2 v5] Driver for Freescale 8610 and 5121 DIU York Sun
2008-03-31 16:23 ` [PATCH 2/2 v5] Add DIU platform code for MPC8610HPCD York Sun
2008-04-01 21:00 ` Andrew Morton [this message]
2008-04-01 21:36 ` Timur Tabi
2008-04-02 13:27 ` York Sun
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=20080401140029.be918d87.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=timur@freescale.com \
--cc=yorksun@freescale.com \
/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).