From: "Mark Chambers" <markc@mail.com>
To: "Fend, Matthias" <mfend@harris.com>, <linuxppc-embedded@ozlabs.org>
Subject: Re: mpc8xx and LCD
Date: Thu, 29 Sep 2005 08:52:08 -0400 [thread overview]
Message-ID: <007701c5c4f4$c7e539c0$0301a8c0@chuck2> (raw)
In-Reply-To: 8D4C69676E66D511A1CB00508BBBB192052D42EF@ranmx1.cs.myharris.net
mpc8xx and LCD>hello,
>We want to use mpc860/855 with a 320x240 graphic lcd module.
>Now there are many possibilities to interface such a module, but I guess
this is not the first time
>someone will need a LCD display. So I'm trying to find out the most common
way to implement the
>desired functionality.
>At the moment I think we should use a lcd controller from Epson (S1D13700
or S1D13305) since they are
>working on Linux framebuffer device driver for it. But I'm not sure how to
design the hardware interface ... all
>the LCD modules I found provide only a reduced number of port pins so that
the controller only can be used
>in indirect-mode, so I'm not sure whether to connect the module directly to
the CPUs bus or use some
>GPIO pins for this...
>Has anybody else implemented a LCD into a mpc8xx (not 823) board
successfully ?
>Are there some good resources somewhere in the web about this topic ?
>thanks for your recommendations,
> mattthias
Can you send a couple of links to the modules you are considering?
Mark Chambers
next prev parent reply other threads:[~2005-09-29 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 6:53 mpc8xx and LCD Fend, Matthias
2005-09-29 12:52 ` Mark Chambers [this message]
2005-09-29 14:03 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2005-09-29 13:45 AW: " Fend, Matthias
2005-09-29 14:44 ` Mark Chambers
2005-09-29 17:31 ` Chuck Meade
2005-09-30 11:07 AW: " Fend, Matthias
2005-09-30 12:50 ` Mark Chambers
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='007701c5c4f4$c7e539c0$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).