It's `frame buffer devices', not `fbcon architectures'. You can have a frame
buffer device without fbcon support, but then you won't have a text console on
it :-)
BTW, I updated the docs at
http://www.cs.kuleuven.ac.be/~geert/Console/
http://www.cs.kuleuven.ac.be/~geert/Console.tex
Expect some patches RSN (I hope, still merging with vger.rutgers.edu-current).
> hours debugging. All you have to provide to be a libGGI
> target is:
>
> * ggiPutPixel
You have to write that yourself. The application should query the frame buffer
device for its memory organization (FBIOGET_FSCREENINFO ioctl), and then you
can select the correct code for that organization.
> * ggiCheckMode
FBIOPUT_VSCREENINFO ioctl, with flag FB_ACTIVATE_TEST.
> * ggiSetMode
FBIOPUT_VSCREENINFO ioctl, with flag FB_ACTIVATE_NOW.
> * ggiPollEvent/ggiReadEvent [mouse/keyboard access]
Use the standard Linux VT stuff.
Greetings,
Geert
-- Geert Uytterhoeven Geert.Uytterhoeven@cs.kuleuven.ac.be Wavelets, Linux/{m68k~Amiga,PPC~CHRP} http://www.cs.kuleuven.ac.be/~geert/ Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium