linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "Fend, Matthias" <mfend@harris.com>, <linuxppc-embedded@ozlabs.org>
Subject: Re: mpc8xx and LCD
Date: Fri, 30 Sep 2005 08:50:12 -0400	[thread overview]
Message-ID: <003301c5c5bd$c0d89f40$0301a8c0@chuck2> (raw)
In-Reply-To: 8D4C69676E66D511A1CB00508BBBB192052D4395@ranmx1.cs.myharris.net

>
> Do you think it's possible to write the device driver in such a way that
> he also translates the pixel data into the indirect register mode of the
> S1D13700 ?
>

No, not directly.  The thing about frame buffer devices is that applications
write directly into the pixel memory (via mmap) so that's why hardware
compatibility is important.  But as Chuck Meade pointed  out, you can make
most anything work by writing a driver that copies from a virtual
framebuffer
to your hardware.

But if this is a new design, forget these indirect chips.  Step one, you
have
to find a controller that can drive your LCD.  Step two, make sure the
controller allows random access to pixels on the host side.  Step three,
if it comes with a driver, great, but if not, framebuffer drivers (for an
LCD)
are pretty simple and you should be able to modify one of the stock
kernel drivers to work for you.  Basically you just have to initialize your
chip and then implement a couple of IOCTLs to query and optionally set
the format of your pixels (and the mmap(), of course).

 --Mark

  reply	other threads:[~2005-09-30 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 11:07 AW: mpc8xx and LCD Fend, Matthias
2005-09-30 12:50 ` Mark Chambers [this message]
2005-09-30 13:55 ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2005-09-29 13:45 Fend, Matthias
2005-09-29 14:44 ` Mark Chambers
2005-09-29 17:31   ` Chuck Meade
2005-09-29  6:53 Fend, Matthias
2005-09-29 12:52 ` Mark Chambers
2005-09-29 14:03 ` Dan Malek

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='003301c5c5bd$c0d89f40$0301a8c0@chuck2' \
    --to=markc@mail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=mfend@harris.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).