Huh? The reply was with regards to all the Selector headaches in
Windows 3.x programming, not the Palm OS. IE, we were talking about the
'386, not the Dragonball.
My point all along has been that the Palm OS uses a simple MMU to help
with data protection and that a more sophisticated MMU (ie, different
hardware) could help more.
Someone pointed out they didn't want segment/selector math headaches. I
was trying to point out that the '386 did not require the VMM/VM scheme
of Windows and that the Palm OS already used a handle concept.
That is not to say that I don't have some criticisms of the Palm OS
memory manager <grin>, just that I hadn't voiced them... <really evil
grin>
Regards,
-jjf
-----Original Message-----
From: Bob Ebert [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 28, 2000 9:00 AM
To: Palm Developer Forum
Cc: Palm Developer Forum
Subject: RE: End Of Dragonball? Palm Shakeup?
At 11:12 PM +0200 04/26/00, Fitzpatrick, Joe wrote:
>You're talking about poorly done software, not a hardware limitation.
Hmm, how do you mean this?
The dragonball processor has some fairly strict limits on the hardware
memory protection it provides. It only has one protected address space,
and that must appear on certain boundaries.
Even using tricks like mapping the same chip to different address
spaces,
there just isn't enough fine granularity allowed to make a given memory
manager chunk writable while protecting everything else. At least, not
with the dragonball.
--Bob
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
