[uae] Re: E-UAE on PalmOS

  • From: Henk Jonas <MetaView@xxxxxx>
  • To: uae@xxxxxxxxxxxxx
  • Date: Fri, 08 Apr 2005 20:33:51 +0200

Hi Richard,

Ok, what I know about it: the armlet is usually part of the main application on a palm. Applications are in a special part of RAM, called storage memory which only can be write-accessed with special OS-functions (they are semaphore protected).

In case of my E-UAE-port, the armlet is seperated and zip packed. The main app will then unzip this armlet into feature memory, which is part of the storage memory, and therefore needs to be write-accessed with this special OS-functions.

As I understand, the usual compiler (or better linker) puts the section for global variables somewhere in the whole executable file. To get it work on Palm OS, when the executable resides in storage memory, one would need to reallocate the section for the global variables somewhere else to allow the processor to actually write something to it.

This sure it can be done for gcc as well, but it's far away from what I want to deal with. So, I wish you luck :-)


Richard Drummond wrote:

Hi Henk

On Thursday 07 April 2005 04:15 am, Henk Jonas wrote:

I use Codewarrior, but the whole E-UAE is made as an Armlet. It could be
done with gcc as well, if someone understands objectfiles and get the
global variable problem solved for Armlets with gcc. I don't understand
much about it. I've just used an enviroment from someone else who
created it for its Doom port.

Okay. I haven't a clue about PalmOS development myself. This might be a good excuse to learn, though. ;-)

I've just downloaded the source and patches to GCC, etc. to build the Palm dev-kit. If I have some time, I'll see if I can get it working...


-- ------------------------------------------------------------------------- Henk Jonas Palm OS ® certified developer

  metaview@xxxxxx                                   www.metaviewsoft.de

Other related posts: