From: "Mark Chambers" <markc@mail.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@ozlabs.org>
Subject: Re: Microwindows on Icecube/CoralP
Date: Mon, 7 Feb 2005 15:30:41 -0500 [thread overview]
Message-ID: <00a001c50d53$e87d4e60$0301a8c0@chuck2> (raw)
In-Reply-To: 20050207195520.D8B4DC108D@atlas.denx.de
>
> This will not work. Microwindows can only use a plain framebuffer
> interface, but the Coral-P does not allow for such a driver because
> of the fact that it has a little-endian register interface.
Or is it because 5200 swaps bytes around on PCI. It sure looks to me
like Freescale has made a major screwup in their implementation of
PCI on the 5200. I'd love for somebody to prove me wrong about this,
but I'm afraid I'm right. I was under the impression that CoralP worked
nicely on 5200, but now I see that it also requires software tweaks to work
on 5200.
Mark Chambers
next prev parent reply other threads:[~2005-02-07 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 10:10 Microwindows on Icecube/CoralP francois.ruvoen
2005-02-07 12:59 ` Mark Chambers
2005-02-07 19:55 ` Wolfgang Denk
2005-02-07 20:30 ` Mark Chambers [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-07 15:24 francois.ruvoen
2005-02-08 7:33 AW: " Martin Krause
2005-02-08 13:12 ` 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='00a001c50d53$e87d4e60$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.