DJWillis wrote:
I guess you must have one of the later backlit ones if it is 3 years old, the screen on them was very nice.
Yep, im still very happy with my BLU. Actually i own two, one for development and the other which i use mostly for mp3 playing, gaming and some divx in my travels to work
![Smile :)](./images/smilies/icon_smile.gif)
I always have appreciatted the battery life and for me it covers much of my needs ... Here in spain you can afford one at a well known online megastore for less than 80$, and it seems they still have lots of second-hand BLUs in stock, ... I smashed two 64 Mbs smc while porting Beat2x, but the gp is still able to access them, and from time to time i find cheap smc's in my city...
![Smile :)](./images/smilies/icon_smile.gif)
... Hope it will be last for long...
DJWillis wrote:
CVS? I assume you mean SVN but that is a rather good situation. If your using the GPSDK I assume your using my EABI versions of the libs? What is output out of interest from the GPSDK build?
Yep it was from SVN... However I realized that everything i have used in gp32 developments (GPTremor, SDL, gdb-stub) are very related to you... So i consider you the "Godfather" of the GP32
![Wink ;)](./images/smilies/icon_wink.gif)
And i am very thankful for your help and suggestions during this time...
Regarding the output of the scumm build (using your EABI libs with the prior release of dkpro) it was more related to initilization of the engine... From there when i tried to enter to the scumm menu appeared some warning which says that the gp were obliged to reboot, but after closing the systems correctly... Not bad at all, however at the GP32 specifics options screen always crashed without warning... I did not debug at all, so it was mostly to test the current state of the engine...
DJWillis wrote:
I would personally be hesitant about using the SDL backend in its entirety but that is only because that every time I tried this it ended up hard against the 8MB limit of the GP32 (much less when you take everything into account) and the less then ideal performance of SDL on the GP32.
It can be done and would be a very nice thing to do but at the very least your going to have to do a build per engine like the DS and do some work creating a hybrid backend of a mixture of SDL, some GP32 specific code and the odd hack
![Wink ;)](./images/smilies/icon_wink.gif)
. Trust me, it is not as bad as I have just made it sound.
fingolfin wrote:
we already have a range of hand optimized ARM assembler routines for blitting, used in other backend.
Well, ill try to do my best on hacking code but i am not that good on ARM assembly
![Sad :(](./images/smilies/icon_sad.gif)
... [@fingolfin] chui's GP32 SDL port also have some ARM code for graphic and sound... Ill compare the ARM versions available in scummvm...
AnywayI still dont know how to performance code or detect memory limits... My experience with the Beat2X port was painfull specially on getting GPTremor to work with the SDLMixer, but i will swear that the generated code using versions of gcc4 works fine, and the tools are still compatible with the GP32 as debug with the EABI versions of GDB works quite well ... I did some tests adding pthread to SDL from sources of the FreeSCI port and seemed to work fine also... My concern around SDL is related to portability, I would love to port more sources rather than stick just to the GPSDK in this project...
DJWillis wrote:
I'll make the same offer I have made to other people who have looked to resurrect the port, I am more then willing to help in any way I can (sans having a GP32) as I would love to see this going again. I still have most of my toolchains setup and as I did a lot of work on the GP32 support for DevKitARM I should be able to help with that also.
Good Luck,
John
I really appreciate your offer, i hope there is no bad sign on trying to keep on with the project... Here goes some questions:
- Build a recent toolchain of DKArm from scratch would be great, with the EABI versions, as i am using the x_gp32library/custom syscalls i have no way to init HW resources on startup but manually,... Ill try by myself anyway, but some help would be ok...
- Also, would you recommend to build from the latest SVN or use a previous stable version? Checking the scummvm documentation i saw that in latest versions is not strictly necessary to use threads, but a clock implementation could be provided, i dont fully understand it but i would try to do some thread testing if it is possible based on the FreeSCI port implementation...
- About debugging, i test directly on HW using insight and the Mithris GDB stub via the pclink cable, its a bit clumsy but works fine for me, so i also need to use part of the EABI-GPSDK, i dont know if there is a better way...
Thanks for everything, ill keep you informed about news...
@B^)>