gsoc2013-patch and questions

[Peng Fan]

I have a few questions about "mmu support".
I read the low level code about mmu  of arm. The map table is statically
set in mem_map, and the initialization code is mmu_init.
All the code realated to mmu is here? If so, thus the flexibility is not so
good. Because when application want to allocate a mem block,
the attributes can not be modified.
The goal of the mmu support is to implemented a well defined framework in
which  middle level  APIs  exposed to application developers, a two level
table implementation  and low level APIs(a common interface that can be
called from middle level apis, I am not sure ). We can use these middle
level  APIs to give each mem block its own attributes.
I am not definitely sure what I think is right.Maybe it's totally wrong.I
just want to give myself a clear understanding.
Thanks for your reply.


2013/3/22 Peng Fan <van.freenix at gmail.com>

> Hi all,
>         I followed the "GSoC_Getting_Started" , modified init.c of the
> hello sample and used "git diff master mybranch" to get the      patch.
>        I am new to gsoc,so there maybe something wrong with what I have
> done.I hope you can point it out.I will appreciate your help.I am
> interested in "mmu support" and "improvements on smp support" listed on the
> "Open projects" page. I am reading the mmu code written in gsoc2012. In the
> code, it uses 1MB section as a unit.Is it coases-grained or too large? why
> not use 4kB page as a fine-grained unit?
>       Anyone can give me some advice about who should i contact about the
> proposal?Thanks very much.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20130322/23434eac/attachment-0001.html>