FB endianness

[Thomas Winischhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Keith Packard wrote:
| Around 3 o'clock on Jan 21, Thomas Winischhofer wrote:
|
|
|>Can you kindly elaborate on this? How? Does this work for 16fbpp and
|>32fbpp? 8bpp clearly wouldn't be a problem.
|
|
| You configure the X server for whatever bit/byte order you want in your
| 32-bit units and then fb draws things in that order, independent of the
| native CPU addressing.


Excuse my eventual ignorance, but I don't see clearly through the whole
fb system.

What exactly do you mean be "configure the X server" in this regard?

How exactly do I tell the fb layer to do as you describe?


| As long as fb accesses memory in 32-bit chunks
| aligned to 32-bit boundaries, it 'just works'.  fb has some accelerated
| code that uses 8 and 16 bit accesses, but you can disable those.

Again, how do I disable those? Are we speaking compile-time or run-time?


| You've certainly got an interesting device there...

It's fun to drive the X infrastructure to its limits ;)

Thomas

- --
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net	       *** http://www.winischhofer.net
twini AT xfree86 DOT org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB8Mm/zydIRAktyUcRAnpdAKDGonwF5vlgtisPq1SbAR1FwbCtsACgu5fO
bs8AppWNhMT3IYXvsbqV9mo=
=bBfn
-----END PGP SIGNATURE-----