I have got GGI/fbdev working on PPC (G-400) by replacing those memsets as
suggested. However I have run into much the same sort of problems when
trying to run XGGI :
>LibGGI: display-fbdev: GGIdlinit start.
L/vtswitch: Unable to get a new virtual console
Linux-kbd: couldn't get mode: Invalid argument
Linux-kbd: couldn't set raw mode: Invalid argument
display-fbdev: Unable to open linux-kbd, trying stdin input.
input-stdin: tcgetattr failed: Invalid argument
input-stdin: tcsetattr failed: Invalid argument
LibGGI: display-fbdev: GGIdlinit success.
LibGGI: display-fbdev: checkmode 800x600#800x600F0[0x20]
LibGGI: display-fbdev: result 0 800x600#800x600F1[0x2002020]
LibGGI: ggiSetMode(0x19f10b0, 800x600.V800x600.F1.D1x1.[C32/32]) called
LibGGI: ggiSetMode: trying (vis 800x600 virt 800x600)
LibGGI: ggiSetMode: trying2 (vis 800x600 virt 800x600)
LibGGI: ggiSetMode: calling 0x14ed888
LibGGI: display-fbdev: checkmode 800x600#800x600F1[0x2002020]
LibGGI: display-fbdev: result 0 800x600#800x600F1[0x2002020]
LibGGI: display-fbdev: setmode 800x600#800x600F1[0x2002020]
LibGGI: display-fbdev: Change mode OK.
LibGGI: display-fbdev: frame_size=0x1d4c00 fb_size=0x1d4c00
mmap_size=0x1d5000
LibGGI: display-fbdev: FB_PTR=0x30027000
Terminating on signal 7
LibGGI: display-fbdev: GGIdlcleanup start.
Terminating on signal 7
Does this mean that XGGI uses the fb directly without using GGI methods? Or
is it a separate problem?
Thanks,
David
