From: Kate Alhola <kate@iti.fi>
To: Stefan Nickl <Stefan.Nickl@kontron.com>
Cc: Wolfgang Denk <wd@denx.de>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Lite5200 PCI not working
Date: Fri, 02 Jul 2004 01:20:13 +0300 [thread overview]
Message-ID: <40E48E1D.4080404@iti.fi> (raw)
In-Reply-To: <1088685514.6235.78.camel@lucy.pep-kaufbeuren.de>
Stefan Nickl wrote:
>On Thu, 2004-07-01 at 13:36, Kate Alhola wrote:
>
>
>>>I've updated the table to include the settings for the Rev. 4.0
>>>board, too, and to list ALL jumpers on the board.
>>>
>>>
>>>
>>>
>>>
>>>>OK. Please see http://www.denx.de/twiki/bin/view/DULG/CoralPInstallation
>>>>
>>>>
>
>Great documentation, thanks!
>
>
>
>>I have Rev 3.0 board with analog switch type EL4331. To get it working
>>even in bypassed mode
>>it needs PD ( Power down ) input in pin 14 to grounded ( connect example
>>to pin 10 ).
>>
>>
>
>The Rev 5.0 board has J251 "PDN EN" (apparently documented nowhere
>except for the DULG) for that purpose. When set, Pin 14 is grounded.
>
>But it didn't help much. I took random shots at the CORALVO[RGB] signals
>on the extension connector, and even there, the red and green channels
>are only half the amplitude as the blue channel with a typical
>grey-on-black linux startup screen. The picture also looks dim-blueish.
>
>
It is wery strange, symproms are exactly sama than with this analog
switch problem
with 3.0 board........
>I think I'll try the board in a Windows box in the next step ...
>
>
>
You can try it in normal PC Linux box also. So did i when i tested
driver before denx driver.
>>With this modification my board works. I am running Embedded QT but it
>>looks a like that
>>#define QT_QWS_REVERSE_BYTE_ENDIANNESS in
>>qt-embedded-free-3.3.2/src/kernel/qgfxraster_qws.cpp was not enough to get
>>colours right. Needs just more hacking code for fixing endianes problem.
>>
>>
>
>We're running qte 3.1.1 on the Asilient chip (cpu is MPC8245),
>and we didn't have to hack Qt for this, hmm ...
>
>
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
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.
Kate
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-01 22:20 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 [this message]
2004-07-01 22:29 ` Wolfgang Denk
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=40E48E1D.4080404@iti.fi \
--to=kate@iti.fi \
--cc=Stefan.Nickl@kontron.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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).