This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: Porting to MMUless PPC
- To: chandra shekar <chandrag at danlawinc dot com>
- Subject: Re: [ECOS] Porting to MMUless PPC
- From: Samuel Tardieu <sam at inf dot enst dot fr>
- Date: Wed, 1 Dec 1999 15:53:36 +0100
- Cc: ecos-discuss at sourceware dot cygnus dot com
- Organization: Ecole Nationale Superieure des Telecommunications
- References: <000901bf3c10$16a7c420$09260cc4@CLUSTER1-3-B.danlaw.stph.net.in>
- Reply-To: Samuel Tardieu <sam at inf dot enst dot fr>
On 1/12, chandra shekar wrote:
| I am trying to port eCos to MPC5XX. It is not having an MMU. Which
| parts of eCos kernel (not HAL layer) call MMU functions defined in the
| file hal_misc.c? 'vectors.S' module of HAL calls them. Can I delete
| those calls without any effect?
Disclaimer: I have not searched in the source, so this answer may be wrong.
As far as I remember, the HAL PPC MMU stuff maps all the zones you give as
executable and read/write, so the goal seems to let the user define a memory
map as well as define what zones should be cached. I cannot see any reason
why the MMU would be further used.