PocketFrog roadmap

Posted:
Jun 11, 2002 @ 11:53am
by Conan
though I can't say why I have found PocketFrog easier to understand than EasyCE & GapiDraw. Unlike PocketGL which took me over a month to figure out ( well it is 3D) I'm getting on well enough to start planning a full game. As mentioned I want to convert Space Treker from PocketC to C++. Much of the code can be copied over though the graphics will be enhanced.
My questions relate to where the toolkit is going so that I don't waste time & duplicate effort.
1. Will the existing structure be changing much in the next few months? ( I don't want to have masses of code to change so some advice here would be useful )
2. Re new features: what functionality will be added in the near future ( to avoid duplication )
3. GAPI for Jornada 720: Do you expect to be able to include this? I'm willing to do anything I'm capable of to assist)
Note: I write big games in my spare time so it can take 6 to 9 months from start to finish.
Regards
Frame buffer on Jornada 720

Posted:
Jun 12, 2002 @ 7:56am
by Conan
I spent a while looking all over & I will aslo e-mail the chap who wrote the existing GAPI for 720.
I found various posts mentioning the same address:-
For 720, the framebuffer is located at physaddr 0x48200000
----------
framebuffer address: 0x48200000
----------
framebuffer: 640x240 type=5 linebytes=1280 addr=0x48200000
---------
+static struct map_desc jornada720_io_desc[] __initdata = {
+ /* virtual physical length domain r w c b */
+ { 0xe8000000, 0x00000000, 0x02000000, DOMAIN_IO, 1, 1, 0, 0 }, /* Flash bank 0 */
+ { 0xf0000000, 0x48000000, 0x00100000, DOMAIN_IO, 1, 1, 0, 0 }, /* Epson registers */
+ { 0xf1000000, 0x48200000, 0x00100000, DOMAIN_IO, 1, 1, 0, 0 }, /* Epson frame buffer */
+ { 0xf4000000, 0x40000000, 0x00100000, DOMAIN_IO, 1, 1, 0, 0 }, /* SA-1111 */
+ LAST_DESC
----------
The epson1356fb.c module depends on the following memory
map (set up near the bottom of arch/arm/jornada720.c):
static struct map_desc jornada720_io_desc[] __initdata = {
/* virtual physical length domain r w c b */
{ 0xf0000000, 0x48000000, 0x00100000, DOMAIN_IO, 1, 1, 0, 0 },
/* Epson registers */
{ 0xf1000000, 0x48200000, 0x00100000, DOMAIN_IO, 1, 1, 0, 0 },
/* Epson frame buffer */
....
};
(The epson chip is at physical address 0x48000000, mapped
to kernel virtual 0xf0000000; the frame buffer for the epson
is at physical 0x48200000, mapped to kernel virtual 0xf1000000 )
Re: Detecting the Jornada I posted the OEM info a couple of weeks back. What else is required.
What's the easiest thing for me to do to test the framebuffer address on my device?

Posted:
Jun 13, 2002 @ 5:30am
by Kzinti
The easiest thing to do if you want to try the framebuffer address is to use SimpleGAPI.CPP instead of the actual GX.DLL.
This can easily be done by modifying a few #ifdefs in GAPILibrary.cpp and SimpleGAPI.cpp.
Once you have enabled SimpleGAPI, you modify GXBeginDraw() to return the framebuffer address. Make sure GXIsDRAMBuffer() returns FALSE and that GXEndDraw() does nothing.
OK. I will have a look when I get time

Posted:
Jun 13, 2002 @ 8:31am
by Conan
Thanks
I will get some time soon to do this after I finish playing with input. I will try to ask as few questions as possible
