From: Kate Alhola <kate@iti.fi>
To: Wolfgang Denk <wd@denx.de>
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 10:55:10 +0300 [thread overview]
Message-ID: <40E514DE.6020300@iti.fi> (raw)
In-Reply-To: <20040702072211.901A5C109F@atlas.denx.de>
Wolfgang Denk wrote:
>In message <40E4E804.5010606@iti.fi> you wrote:
>
>
>>Do you meaean that responsibility of byte order is left to application
>>level ?
>>
>>
>
>No. The graphic drivers are responsible for it.
>
>
It is how you call it. X server or Embedded QT graphics driver normally
works
in user level..
>>Linux fbdev just maps display memory to user application space and so it
>>cant do anything for how R,G,B bits are ordered within word. It is
>>then responsibility to GUI-engine ( X-server, Embedded-QT ) to
>>handle this ordering.
>>
>>
>
>This is why it is impossible to use a simple framebuffer driver on
>the Coral-P in 16 bit mode. You can run a framebuffer with 24 bpp
>(and actually our first demo dreiver was doing this), but it ain't no
>fun.
>
>
Yes, this was that i were using and in this one x-server was just
patched to fix byte order.
>Also, with a framebuffer driver you miss all the options for
>accelerated graphics provided by the Coral-P engine.
>
>This is why we implemented an accelerated X11 driver for the Coral-P.
>
>
I should try this new one. With the older one i have some problems with
get all required
virtual console etc drivers to compiled to kernel to make Xfree 4.4
happy. Ok, now
there looks a like to be icecube_5200_CoralP_defconfig
It is just somehow dificult to find all new files appearing to tree ......
May be it is worth to try use QT with X11 server instead using embedded
qt direct to
fb device. In older driver it was anyhow much better to use embedded qt
direrctly.
Kate
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-02 7:55 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
2004-07-02 4:43 ` Kate Alhola
2004-07-02 7:22 ` Wolfgang Denk
2004-07-02 7:55 ` Kate Alhola [this message]
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=40E514DE.6020300@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).