rlyeh said:
what u guys rather like dingux or native?
Actually I think this is a tough question. The A320 Dingoo is nice, but honestly I think it may have a short lifespan.
The problem is that there is no standard. Game and emulators have been released for both - native and dingux.
Dingux would be my preference, but I fear that some of it's issues will not be resolved in a good amount of time.
I'm not knocking Booboo, he's done a great job getting Dingux to where it is now, but there still seems to be a lot to do.
Even relatively simple things like double buffered screens are still not available. :-(
rlyeh said:
should i compile staticly or dinamicly?
I think for Dingux you should dynamically compile - I've released both static and dynamic compilations.
rlyeh said:
whats the minimal library/low level library of your choice?
I've ported across your very own minimal lib from GP2X to A320. I guess you'd like to have it back? It's strictly for Dingux at the moment.
rlyeh said:
have we got a vsync routine already?
There will never be a v-sync. It's a hardware limitation. The necessary hardware is not in place. There maybe a way to do it like the old GP32 - create a very accurate timer - but as far as I know, no one has done this yet.
rlyeh said:
and a true hw timer routine? how is the reset button mapped?
Dingux uses clcok();
rlyeh said:
has the video chipset some kind of hardware strecthing? and blitter?
Yes there is, it's not enabled in the standard kernel for Dingux, though I think you can access it natively.
rlyeh said:
can we set the video to work in real 8bpp? same for sound, can we set it to real 8 bit?
8-bit video only works for TV out. The reason is that there are two screen controllers, one for the TV another for the LCD. The LCD work with 16-bit.
8-bit sound should be supported under Dingux.