On Fri, 14 Jul 2000, �iogo Sperb Schneider wrote:
[about MMU]
> Ok, but I still don't see how it could not be
> implemented in software.
How could you avoid programs to access memory areas that don't belong to
them if your MMU is implemented in software? How could you stop user
programs to overwrite the MMU code and make it work as the user want?
> > And I think it should not be implemented in the new
> > MSX. It would make
> > programming MUCH harder,
>
> Why? I thought programming in C was a well known art.
Low-level kernel routines, such as the MMU and low-level scheduler code is
written in assembler, even in your beloved Linux. But that's not the
problem, because most members of this list have mastered ASM programming
in the MSX. The problem is that you can't do it in software.
--
[EMAIL PROTECTED] - http://www.aamsx.org
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
