Given that they said they're unwilling to make the reset hole bigger I would kind of think that things like this are out. Same goes with any other physical modifications whatsoever. Maybe in a later revision, but given how long it took them to make GP2X F200 even though they were addressing some basic problems that desperately needed fixing I wouldn't expect anything anytime soon. I don't think this thread is for suggestions for something like that.
I'm sure GPH has their own program to test apps on their computer, couldn't they release it for devs and concerned end-users? I mean, they are all about open-source and everything, right?
Then how would they test their own programs and firmwares? By bricking a whole unit over and over again until they get it right?
I dont think you understand embedded development. They have the tools to develop the pollux boards. They can simply replace and fix any part of the bootloader/kernel when they need to. When you only have the wiz by itself and no source, then its gets difficult.
Wiz software is the combined efforts of many companies who don't know how to program well.I think that a third party is doing the firmware related thing, look for the logo in the loading....
That made me chuckle quite a bitWiz software is the combined efforts of many companies who don't know how to program well.I think that a third party is doing the firmware related thing, look for the logo in the loading....
.
It makes me wonder why they don't release the tools and barebone firmware and such to the hobbyist developers. They're selling the hardware, right? Why sell a product with poorly developed software? That's like selling a quad core PC and having it ship with Windows ME.
Or vista. LOL
They really don't have any tools of their own. The only thing they hold is the datasheet/programming manual for the system on chip they're using, but actually, the manufacturer of that keeping it secret is quite bizarre and not at all typical for SoC's. I've looked at many of them and I wouldn't ever dream of making a purchasing decision for an evaluation module, much less a design decision without knowing the full details of the programming interface of the chip beforehand. Of course there are exceptions, like the SGX on OMAP3530.. but that's a cross-licensing situation.
So basically...
Aye, so the people we should be asking for updates from would be MES then, right?
gp2xmenu should check the presence of an autorun.gpu file in /mnt/sd/ each time it is run, so that custom menus are viable alternatives to the stock one. This really should be easy to implement, and it would bring a lot of good things in return.
