linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Kate Alhola <kate@iti.fi>
Cc: Stefan Nickl <Stefan.Nickl@kontron.com>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Lite5200 PCI not working
Date: Fri, 02 Jul 2004 00:29:33 +0200	[thread overview]
Message-ID: <20040701222938.2B62CC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 02 Jul 2004 01:20:13 +0300." <40E48E1D.4080404@iti.fi>


In message <40E48E1D.4080404@iti.fi> you wrote:
>
> There is generic problem in these Fujitsu Display cobntrollers chips
> that their
> byte ordering (endianism) does not match with powerPC. So when used
> in 32 bit pixels the R, G and B bytes does not match normal way used by
> linux Frame buffer devices. Most of  chips allow configuration for little or
> big endian based on CPU but CoralP does not and this conversion must be
> done by software. For this reason we are offering two display controller

That's  why  we  implemented  drivers  fopr  the  Coral-P  which  are
independedt of the byte-order (and available under GPL).

> solutions, CoralP and Rage Mobility M1.  There is some good things in
> COralP and at the moment it is only chip specified for
> extended temperature range.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Until you walk a mile in another man's moccasins, you  can't  imagine
the smell.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-01 22:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01  9:18 Lite5200 PCI not working Wolfgang Denk
2004-07-01 11:36 ` Kate Alhola
2004-07-01 12:38   ` Stefan Nickl
2004-07-01 22:20     ` Kate Alhola
2004-07-01 22:29       ` Wolfgang Denk [this message]
2004-07-02  4:43         ` Kate Alhola
2004-07-02  7:22           ` Wolfgang Denk
2004-07-02  7:55             ` Kate Alhola
2004-07-02  8:51               ` Wolfgang Denk
2004-07-02 11:35                 ` Lite5200 CoralP issues Kate Alhola
2004-07-02 13:46                   ` Mark Chambers
2004-07-02 14:51                     ` Wolfgang Denk
2004-07-08 11:57             ` Lite5200 PCI not working Stefan Nickl
2004-07-08 12:12               ` Wolfgang Denk
     [not found] <20040708124140.E18E4C109F@atlas.denx.de>
2004-07-08 13:34 ` Stefan Nickl
  -- strict thread matches above, loose matches on Subject: below --
2004-06-21 11:12 Iñigo Lopez Barranco
2004-06-21 11:48 ` Gerhard Jaeger
2004-06-21 10:03 Iñigo Lopez Barranco
2004-06-21 10:26 ` Gerhard Jaeger
2004-06-21 10:53   ` Wolfgang Denk
2004-06-21 11:39     ` Gerhard Jaeger
2004-06-21 14:12     ` Kate Alhola
2004-06-21 15:14       ` Wolfgang Denk
2004-06-21 16:20         ` Kate Alhola
2004-07-01  8:41           ` Stefan Nickl
2004-07-01  8:52             ` Wolfgang Denk
2004-06-21 10:51 ` Wolfgang Denk
2004-06-21 19:19 ` Mark Jonas
2004-06-22  6:08   ` Gerhard Jaeger

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=20040701222938.2B62CC109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Stefan.Nickl@kontron.com \
    --cc=kate@iti.fi \
    --cc=linuxppc-embedded@lists.linuxppc.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 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).