Sir,

Thanks for your time and consideration. I was discussing this project with
Gedare Sir and he guided me, how to proceed.
I am studying various things before proceeding with the code part but for
now, I request you to please guide me what should be my next steps to work
on this project under GSOC'18.

Thanks and Regards
Abhinav Jain

On Sun, Mar 4, 2018 at 10:48 AM, Hesham Almatary <heshamelmat...@gmail.com>
wrote:

> On Sun, Mar 4, 2018 at 10:20 AM, Joel Sherrill <j...@rtems.org> wrote:
> >
> >
> > On Mar 3, 2018 12:16 PM, "Abhinav Jain" <jainab.2...@gmail.com> wrote:
> >
> > Sir/Madam,
> >
> > I am Abhinav Jain, a second-year engineering student from Delhi, India. I
> > have been working in Linux Kernel Development, I have been writing small
> > drivers and have a good knowledge of the operating system.
> > I have been studying about Memory Protection project(ticket #2904) for
> > around a month and found it really interesting. I studied about POSIX,
> MMU
> > support in various other architecture and the memory protection APIs in
> > various operating systems.I have been discussing the same on the mailing
> > list.
> > I also solved an issue (#2522) around a week ago to gain some hands-on
> code.
> >
> >
> > Welcome aboard.
> >
> >
> > I would like to work on the Memory Protection project under GSOC 2018,
> so I
> > request you to please guide me regarding the steps to be followed.
> >
> >
> > Gedare conceived of what's there be so I cc'ed him. My recollection is
> that
> > there were specific things he wanted to change and when that was
> addressed,
> > providing support for arenas on multiple architecture is desirable
> >
> +1
>
> There might be an opportunity to port RTEMS to RISC-V's Supervisor
> Mode which will need MMU support (currently it only runs on M-Mode
> which doesn't have MMU). Both QEMU and Spike simulators support
> S-Mode.
>
> >
> >
> > Thanks and Regards
> > Abhinav Jain
> >
> > _______________________________________________
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
> >
> >
> >
> > _______________________________________________
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
>
>
>
> --
> Hesham
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to