> Yes, we're doing so, with a new mechanism that will fit the new OS's
> mechanism. It just didn't make sense to cripple Palm OS 5 by having
> it continually call from ARM back into 68k code all the time -
> there's a lot of context to bring up and down.
That could have been avoided by requiring that on OS5 any system trap
replacement must be a native ARM routine. If you don't want two versions of
the hack (one m68k for pre-OS5 and one ARM for post), a small stub at the
beginning of the routine to switch to a 68k or an ARM version of the routine
as appropriate is simple enough to do, assuming that the compiler could be
updated to support generating this:
("common" is the entry point to the joint routine)
m68k ARM
m68jmp: 60 00 xx xx BRA m68rtn
common: 60 FA 00 FF BRA m68jmp NOP (SWI with a "never" condition)
armrtn: ..... The real ARM code
...
m68rtn: ..... The real m68k code
Having said that, there's still an argument for replacing the current system
with a more controlled mechanism for patching the OS, but it would have been
nice if it were in place before the old system was removed :-)
So how soon are we likely to see this new mechanism? Will it be part of a
free OS update for those of us who have already gone out and bought our
Tungstens?
Cheers,
Matthew
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
