public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Cc: linux-fbdev-devel@lists•sourceforge.net, adaplas@gmail•com,
	Suneel <suneelg@xilinx•com>,
	akonovalov@ru•mvista.com, John Linn <john.linn@xilinx•com>
Subject: Re: [PATCH] [V5] Xilinx : Framebuffer Driver: Add PLB support and cleanup DCR
Date: Fri, 24 Apr 2009 13:01:58 +0200	[thread overview]
Message-ID: <200904241301.59775.arnd@arndb.de> (raw)
In-Reply-To: <20090417205119.3D35660055@mail16-sin.bigfish.com>

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

On Friday 17 April 2009, John Linn wrote:
> Added support for the new xps tft controller. The new core
> has PLB interface support in addition to existing DCR interface.
> 
> Removed platform device support as both MicroBlaze and PowerPC
> use device tree.

I just said in another email thread that we would need a CONFIG_DCR
option that DCR using drivers should depend on, if it ever happened
outside of powerpc.

Well, apparently this happened earlier than I expected.

Converting the driver to use the generic DCR interface
makes it possible to use in any system that provides this
interface, including those that use a hard CPU core with xilinx_fb
on an FPGA, so it makes sense to just change the dependency
in Kconfig and provide CONFIG_DCR in microblaze (unconditionally)
as well as in powerpc instead of the existing CONFIG_PPC_DCR.

	Arnd <><

[-- Attachment #2: Type: text/html, Size: 4265 bytes --]

  reply	other threads:[~2009-04-24 11:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 20:51 [PATCH] [V5] Xilinx : Framebuffer Driver: Add PLB support and cleanup DCR John Linn
2009-04-24 11:01 ` Arnd Bergmann [this message]
2009-04-27 12:58   ` Benjamin Herrenschmidt

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=200904241301.59775.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=adaplas@gmail$(echo .)com \
    --cc=akonovalov@ru$(echo .)mvista.com \
    --cc=john.linn@xilinx$(echo .)com \
    --cc=linux-fbdev-devel@lists$(echo .)sourceforge.net \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=suneelg@xilinx$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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