Search results

I would really love to be able to boot a small SD card directly, just like popping a game into a gameboy. And what a rush it would be to be able to test your OWN programs this way. GPH should implement this as a standard feature!

hi, i just couldn't help but notice... but ... looks like basically everything about the gp2x is lousy... - bad case... - screen issues... - bad joystick... - badly placed power jack... - bad headphone jack... - bad usb file transfer support... - long boot time... - bad sd support... - bad...

this is silly. no, i mean, seriously - what's the point. you'd call this, with all those preconceived conventions, "free" development? :rolleyes: better if you at least call them "suggestions" rather than "guidelines" - and present them as opinion based on some evidence... not "official"...

hey, the functions of the SDK could be importable into an assembly program, right? the reason i ask is i would prefer writing direct ARM assembly program rather than C. (it is a personal opinion, so I hope C adherants wouldn't judge it.)

(erased) ... nevermind! i just read the "any news on HH" thread again and realized my oh so special idea was already being done.

In preperation for my acquisition of a gp2x i wanted to take the time to get the info on SD cards and possibly grab one while they're cheap on ebay. who knows how the demand will rise once gp2x is fully released and becomes a househole brand? ;-) so, the basics. what SD cards work, and what...

who's in charge of writing the SDK? from where is he/she (if it's not gph) getting their documentation? i'm looking for low-level info on the gp2x. thanks...

oh, ok. that's helpful. (!sarcastic) could an HH game access data from the flash drive without linux? like say, through the bios, or directly. i have a bunch of other questions now, but i think i should probably open up a topic devoted to them when i get around to it.

what exactly are the services linux provides in the background of a "normal" application? also does HH (or HHB now, whatever) code need to be "relocatable"? (not that it matters all that much for the second one, just wondering and trying to get an idea of the difference)

but you've missed the all important question - how badly do you even really WANT to play games made for 640x480 on the gp2x? not to say that the hardware scaler isn't useful...

Hmm. What size SD cards do you all use? I was thinking of buying just a teeny one (32mb) to start with, and then move up to 1 or 2 GB when i have the money to waste. (mainly to store mp3's etc) :)

a valid point. sometimes reinventing the wheel is not what you want to do! one of my options is to write the forth for Linux/GP2X for starters, and then think about native boot. I just don't know which one will be less challenging. the setup code for a Linux-based app can't be negligible...

I'm interested in HH to do a native GP2X Forth one day. Everything can be done in 1% the code. SDL and Linux require more code. with SDL, a C program to draw a pixel onto the screen requires +20 lines of code. In Forth it is possible in 1. Forth is just one of the reasons why HH is needed...

heheh. well, duh. :P i only asked because i am attracted by the idea of replacing the OS with a work of my own. but maybe it isn't worth it, since i would be losing all the power of the Linux OS. and the libraries too, i guess? so how DO you get program files into the machine?

still, that's awesome, and very useful to know. come on though, isn't it like 1000+ writes or something? i do plan on getting a mem card eventually. btw can you boot programs via USB straight to RAM? do programs have to be run through Linux?

I noticed that on the GBAX website that in the order page it says the Gp2x has "64m internal storage" does that mean the GP2X comes with 64 MB RAM as well as 64 MB FLASH? what's the story?