This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Is there any MMU support on eCOS?
- To: Mehran_M1 at Verifone dot com
- Subject: Re: [ECOS] Is there any MMU support on eCOS?
- From: Bart Veer <bartv at redhat dot com>
- Date: Fri, 24 Aug 2001 15:57:29 +0100
- Cc: ecos-discuss at sourceware dot cygnus dot com
- References: <E983B3C43329D111AA720060B06C9D8802748EB4@lon-nt-mail1.verifone.com>
- Reply-To: bartv at redhat dot com
>>>>> "Mehran" == Mehran Mirkazemi <Mehran_M1@Verifone.com> writes:
Mehran> Dear All Sorry for asking this naive question, but am I
Mehran> correct in assuming that eCOS does not use MMU
Mehran> functionality provided by some processors to provide
Mehran> application/task fire-walling?
Mehran> I have not seen any mention of this support on the Red hat
Mehran> site, but on another site some one mentioned that eCOS
Mehran> supports MMU.
The model for a typical eCos system involves a single application,
linked directly with eCos. That application is likely to be
multi-threaded, but all threads run in a single address space. With
only a single application there is little point in setting up the MMU
to provide protection between applications :-) Some more information
can be found in the ecos-discuss archives, for example
http://sources.redhat.com/ml/ecos-discuss/1998/msg00062.html
For architectures where an MMU is built-in, eCos will either ignore
the MMU completely or, more commonly, perform just enough
initialization so that the system works and the application sees a
simple linear address space.
I am aware of efforts to make more use of MMUs,
http://sources.redhat.com/ml/ecos-discuss/2001-03/msg00089.html.
Bart