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

Somebody in the thread at some point said:

| | aware. Further, in this approach we at least double the framebuffer
| | memory consumption (likely more than double depending on what happens
| | with timing). So 800x600x3bytesx2 = 4MB just for framebuffer.

BTW are you talking about E-ink virtual framebuffer?  You won't need
this kind of bit depth for that?  1 byte is just 480KBytes for 800 x 600.

The LCD framebuffer on GTAxx is 640x480 anyway, in 666 mode / 24-bit
it's < 1Mbyte.  If your command is longer, you can issue a blank raster
while you compose the next frame, the controller shouldn't care because
we control the write signal for the bus.

You only need page flip (is that why you doubled this number?) in Glamo
case, because you don't have usable VSYNC interrupt, so using this lets
you be sure you issue just one frame easier.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmeRcIACgkQOjLpvpq7dMrrDwCdGZQRdl6rwNAvNtNpkiM7opCe
rAwAnAxSuxVfq6LC1re8T1d0uCX7tOCD
=8gg4
-----END PGP SIGNATURE-----

_______________________________________________
hardware mailing list
hardware@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/hardware

Reply via email to