From: "Lorenz Kolb" <linuxppcemb@lkmail.de>
To: <linuxppc-embedded@ozlabs.org>
Subject: Re: Using Xilinx Framebuffer on ML405 and 2.6.20.4
Date: Tue, 24 Apr 2007 17:07:57 +0200 [thread overview]
Message-ID: <000001c78682$5e6a3e40$1b3ebac0$@de> (raw)
In-Reply-To: <mailman.1028.1177426735.26657.linuxppc-embedded@ozlabs.org>
> Message: 1
> Date: Tue, 24 Apr 2007 17:58:13 +0400
> From: Andrei Konovalov <akonovalov@ru.mvista.com>
> Subject: Re: Using Xilinx Framebuffer on ML405 and 2.6.20.4
> To: Grant Likely <grant.likely@secretlab.ca>
> Cc: linuxppc-embedded@ozlabs.org
> Message-ID: <462E0CF5.4060402@ru.mvista.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Grant Likely wrote:
>> On 4/24/07, Peter Mendham <petermendham@computing.dundee.ac.uk> wrote:
>>> Dear all,
>>>
>>> I am wanting to use the Xilinx TFT controller from the ML403/5 reference
>>> project (probably from ML300 as well) under a 2.6.20.4 kernel. I have
>>> Grant Likely's patchset applied in which there is a platform device
>>> entry for the framebuffer. Does anyone know if there is mainline
>>> support for the Xilinx-style framebuffer? If so, how do I enable it? I
>>> have included framebuffer support in my kernel build, but I assume I
>>> need a driver also? Any tips greatly appreciated.
>>
>> Heh, I've got a driver. I just haven't published it yet. Give me a few
days...
>>
>> g.
>>
>
> We have one too :)
To be continued: we have one too :)
I guess fb support is too simple, as too many people have wrote that driver
...
Greetings,
Lorenz
next parent reply other threads:[~2007-04-24 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1028.1177426735.26657.linuxppc-embedded@ozlabs.org>
2007-04-24 15:07 ` Lorenz Kolb [this message]
2007-04-24 9:13 Using Xilinx Framebuffer on ML405 and 2.6.20.4 Peter Mendham
2007-04-24 13:38 ` Grant Likely
2007-04-24 13:46 ` Peter Mendham
2007-04-24 13:58 ` Andrei Konovalov
2007-04-24 13:54 ` Peter Mendham
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='000001c78682$5e6a3e40$1b3ebac0$@de' \
--to=linuxppcemb@lkmail.de \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.