This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Regd. the MMU in eCos1.3.1
- From: Rajan Srivastava <rajan at cdotd dot ernet dot in>
- To: eCos <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 4 Apr 2003 12:09:49 +0500 (GMT+0500)
- Subject: [ECOS] Re: Regd. the MMU in eCos1.3.1
- >received: from sagit.cdotd.ernet.in by cdotd.cdotd.ernet.in (SMI-8.6/SMI-SVR4)id MAA06233; Fri, 4 Apr 2003 12:08:48 -0500
Hi,
The query launched by Mr Prabal is very much valid.
In follow-ups, it is said that why at all memory locking
is needed, let me elaborate the need.
Suppose I want some data to be protected against
accidental writes. If the page/segment is write protected,
eCos could generate an exception (write attempt on
RO page/segment) when some thread tries to
write on this area due to some coding bug.
So testing will become very easy.
Kindly see that eCos is getting so popular that
it has been widely accepted for realtime
embedded softwares, so these kind of lock
requirements should be met.
Or you can guide us, how to write memory locking for
a given processor, eCos too can accept
this facility in its overall source-code
Regards
Rajan
-------
Rajan Srivastava, Co-ordinating Engineer (VMS/UMS)
Centre for Development of Telematics (C-DOT)
-----------------------------------------------------------------------
Address : Room No - 926, C-DOT, Akbar Bhawan, Chanakyapuri, New Delhi.
Phone No: 011-24678974 (Direct), 011-24677525 Extn-226
-----------------------------------------------------------------------
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss