From: Dan Malek <dan@embeddededge.com>
To: "Fend, Matthias" <mfend@harris.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: AW: mpc8xx and LCD
Date: Fri, 30 Sep 2005 09:55:43 -0400 [thread overview]
Message-ID: <ed8744038b59c4ab9bc4a9bfa9f4ebd8@embeddededge.com> (raw)
In-Reply-To: <8D4C69676E66D511A1CB00508BBBB192052D4395@ranmx1.cs.myharris.net>
On Sep 30, 2005, at 7:07 AM, Fend, Matthias wrote:
> As I know at least the S1D13700 is brand new (the people from Epson
> are working
> on a
> Linux driver at the moment).
OK.
> 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 ?
The only way I can think of is to access protect the "frame buffer",
trap all accesses and then do some translation in software. Very, very
slow and inefficient. The most efficient way is for applications (like
X)
to do this internally.
> ? You mean the 823 has an internal LCD controller -
Yes.
> ..... I know that but I want to
> use a 860 or 855 (we already use them in other products).
Oh well .... :-)
> Do you think it would be the best way to use an 823 and a driver-only
> display ?
I don't understand the question.
> As there are so many devices with LCD display in use, I thought there
> could be a
> an easy going standard solution for this, but it seems to be a little
> bit tricky
There is a standard. Attach your graphics device to the processor bus
as
a memory mapped device and use a Linux frame buffer :-) The complexity
of your graphics requirements will determine how much additional
software
you have to write. Since I like to use X-windows, most of the software
I
end up writing is in that server, not the Linux driver.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-09-30 13:55 UTC|newest]
Thread overview: 4+ 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
2005-09-30 13:55 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-29 13:45 AW: " Fend, Matthias
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=ed8744038b59c4ab9bc4a9bfa9f4ebd8@embeddededge.com \
--to=dan@embeddededge.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).