Re: Interested in GSoC 2017 Project: Memory Protection.

Trying to review your proposal: 1) You've to allow comments/edit so that we can give feedback. 2) The proposal is not complete, you copied the template and didn't update all of the sections. On Thu, Mar 30, 2017 at 8:27 AM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > Hello Dr.

Re: Interested in GSoC 2017 Project: Memory Protection.

Hello Dr. Bloom and other folks, I have developed an initial draft of my application, kindly review it. I can be more verbose in explaining the granular details regarding the concepts and approaches, so kindly tell me how and where I can amend the proposal. On Sat, Mar 25, 2017 at 12:15 PM, Hesha

Re: Interested in GSoC 2017 Project: Memory Protection.

On Sat, Mar 25, 2017 at 6:07 AM, Gedare Bloom wrote: > Work on shaping your proposal document and start to plan the work you > would do during the summer. This is the best way for me to collaborate is > if you begin writing out your ideas in sufficient detail that I can > understand and provide f

Re: Interested in GSoC 2017 Project: Memory Protection.

Work on shaping your proposal document and start to plan the work you would do during the summer. This is the best way for me to collaborate is if you begin writing out your ideas in sufficient detail that I can understand and provide feedback based on where you are at. On Fri, Mar 24, 2017 at 11:

Re: Interested in GSoC 2017 Project: Memory Protection.

Hello Dr. Bloom, I have contacted to the past contributors, Peter and I will discuss PowerPC and further support, next week, in the meantime, I am going through PowerPC code and how I can build with the existing system a new bsp code for MMU/MPU support. I will complete my application next week.

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 11:13 AM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > Indeed, PowerPC code is somewhat developed, would you recommend if there > are some specific features in PowerPC that I should revisit? As this is > little confusing as some work has been done on except

Re: Interested in GSoC 2017 Project: Memory Protection.

Indeed, PowerPC code is somewhat developed, would you recommend if there are some specific features in PowerPC that I should revisit? As this is little confusing as some work has been done on exception handler, page tables, cache already, so what should I target next and what to modify first? Past

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 10:07 AM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > > On Wed, Mar 22, 2017 at 7:17 PM, Gedare Bloom wrote: > >> Please prefer to try to keep general GSoC / RTEMS project discussions on >> the mailing list. Direct e-mail is ok but inefficient in many cas

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 10:41 AM, Joel Sherrill wrote: > I may have missed this but Gedare has been working on adding > the mmap/shm services from POSIX. It would be nice for the > dynamic changes interface he mentioned to have an interface > to these calls. I am sure Gedare has thought of how th

Re: Interested in GSoC 2017 Project: Memory Protection.

Hello Dr. Joel, Dr. Bloom obviously have this approach lined up, and that is why he advised me to go work on the low level support for some more bsp's in order to start supporting a firm MMU/MPU interface to applications running. I guess now I need to support more bsp's in order to get to a pragma

Re: Interested in GSoC 2017 Project: Memory Protection.

I may have missed this but Gedare has been working on adding the mmap/shm services from POSIX. It would be nice for the dynamic changes interface he mentioned to have an interface to these calls. I am sure Gedare has thought of how this would work already. :) --joel On Thu, Mar 9, 2017 at 1:14 PM

Re: Interested in GSoC 2017 Project: Memory Protection.

On Wed, Mar 22, 2017 at 7:17 PM, Gedare Bloom wrote: > Please prefer to try to keep general GSoC / RTEMS project discussions on > the mailing list. Direct e-mail is ok but inefficient in many cases and > should only be preferred for communciations of a personal or private matter. > > On Wed, Mar

Re: Interested in GSoC 2017 Project: Memory Protection.

On Thu, Mar 16, 2017 at 1:05 PM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > Hello Dr. Bloom, > > Sorry for writing after a big gap( was busy with a product integration), > although I found time to go through the pointers you put together for me, > thanks they were really helpful

Re: Interested in GSoC 2017 Project: Memory Protection.

Hello Dr. Bloom, Sorry for writing after a big gap( was busy with a product integration), although I found time to go through the pointers you put together for me, thanks they were really helpful in getting an idea about the project and how to process everything in time. I noticed that all the ex

Re: Interested in GSoC 2017 Project: Memory Protection.

On Thu, Mar 9, 2017 at 2:14 PM, Abhimanyu Rawat < h2015...@pilani.bits-pilani.ac.in> wrote: > Hello folks, > > I am Abhimanyu Rawat, a Computer Science Masters degree student from BITS > Pilani Campus, India. I found Memory Protection project #2904 > very inte

Interested in GSoC 2017 Project: Memory Protection.

Hello folks, I am Abhimanyu Rawat, a Computer Science Masters degree student from BITS Pilani Campus, India. I found Memory Protection project #2904 very interesting and vital for the the RTEMS. Among the lots of projects listed on the ideas page, Memory Prote