On Sat, Jul 18, 2020 at 3:55 AM Utkarsh Rai wrote:
>
>
>
> On Sat, Jul 18, 2020 at 1:21 PM Hesham Almatary
> wrote:
>>
>> We have already discussed and done that during my 2013 GSoC. Have a
>> look at [1, 2] and their calls.
>>
>> [1]
>> https://github.com/heshamelmatary/rtems-gsoc2013/blob/low
On Sat, Jul 18, 2020 at 1:21 PM Hesham Almatary <
hesham.almat...@cl.cam.ac.uk> wrote:
> We have already discussed and done that during my 2013 GSoC. Have a
> look at [1, 2] and their calls.
>
> [1]
> https://github.com/heshamelmatary/rtems-gsoc2013/blob/low-level-libmm/cpukit/score/include/rtems/
We have already discussed and done that during my 2013 GSoC. Have a
look at [1, 2] and their calls.
[1]
https://github.com/heshamelmatary/rtems-gsoc2013/blob/low-level-libmm/cpukit/score/include/rtems/score/mmimpl.h
[2]
https://github.com/heshamelmatary/rtems-gsoc2013/blob/low-level-libmm/cpukit
Hello,
In RTEMS each set of BSP has its own MMU implementation, for utilizing this
for high-level operations such as thread-stack protection we need a common
interface that is implemented for each BSP but is available for high-level
operations ( Something along the lines of the cache manager ), my
