linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Xilinx: framebuffer: add compatibility for ml507 dvi core.
Date: Mon, 12 May 2008 08:24:41 -0600	[thread overview]
Message-ID: <fa686aa40805120724u17a380adnd0826044ae3ac369@mail.gmail.com> (raw)
In-Reply-To: <20080505175918.2AD03A58056@mail164-sin.bigfish.com>

On Mon, May 5, 2008 at 11:59 AM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
> Signed-off-by: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
>  ---
>   drivers/video/xilinxfb.c |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
>  diff --git a/drivers/video/xilinxfb.c b/drivers/video/xilinxfb.c
>  index 848752e..a82c530 100644
>  --- a/drivers/video/xilinxfb.c
>  +++ b/drivers/video/xilinxfb.c
>  @@ -396,6 +396,7 @@ static int __devexit xilinxfb_of_remove(struct of_device *op)
>   /* Match table for of_platform binding */
>   static struct of_device_id xilinxfb_of_match[] __devinitdata = {
>         { .compatible = "xlnx,plb-tft-cntlr-ref-1.00.a", },
>  +       { .compatible = "xlnx,plb-dvi-cntlr-ref-1.00.c", },

Can you get the dvi core to claim compatibility with the tft core
(assuming it is register level backwards compatible)?

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-05-12 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 17:59 [PATCH] Xilinx: framebuffer: add compatibility for ml507 dvi core Stephen Neuendorffer
2008-05-12 14:24 ` Grant Likely [this message]
2008-05-12 17:31   ` Stephen Neuendorffer
2008-05-12 18:30     ` Grant Likely
2008-05-12 19:10       ` Stephen Neuendorffer
2008-05-12 19:46         ` Grant Likely
2008-05-12 19:59           ` Stephen Neuendorffer
2008-05-14 15:35             ` Grant Likely
2008-05-14 18:03               ` Stephen Neuendorffer

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=fa686aa40805120724u17a380adnd0826044ae3ac369@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stephen.neuendorffer@xilinx.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).