Re: GSoC 2018 project announced

Yes I have received the mail Thank you! On Tue, 24 Apr 2018, 20:15 Gedare Bloom, wrote: > All students should have received an email from me today about how to > proceed. > > On Mon, Apr 23, 2018 at 5:43 PM, Vijay Kumar Banerjee > wrote: > > Hello mentors, > > > > Thank you for letting me hav

Re: GSoC 2018 project announced

All students should have received an email from me today about how to proceed. On Mon, Apr 23, 2018 at 5:43 PM, Vijay Kumar Banerjee wrote: > Hello mentors, > > Thank you for letting me have this wonderful opportunity to work with RTEMS > under the GSoC 2018 program!! > > I would like to ask abou

Re: Gsoc 2018

Check out the csv file in rtems-docs/posix-compliance. Chris and I put together a new POSIX Compliance Guide. It is on docs.rtems.org. Check out the guide and the new csv. Up to date and lots of POSIX profiles. :) Even has guidance on finding methods to implement. Between that and the ticket, sho

Re: Gsoc 2018

Are you interested in the POSIX Compliance project? If so, you really need to get your proposal together and submitted. Then we can worry about doing the work proposed. With no proposal, you can't get accepted. https://devel.rtems.org/ticket/2966 is the POSIX Compliance ticket. It has sub-tickets

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

I like the sound of that! One quick question. > ...to get it running on qemu. Real HW would be a sanity check. What kind of real hardware would I need? I do have an x86 64-bit processor as my primary computer, and likely one on spare / abandoned devices too (though I'll need to confirm). Is there

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mar 13, 2018 1:36 AM, "Sebastian Huber" < sebastian.hu...@embedded-brains.de> wrote: On 12/03/18 21:20, Gedare Bloom wrote: > Since I'm pretty keen on RTEMS, I think I'll have a 2nd proposal too, which >> I'll decide and discuss with you guys soon, hopefully! (Perhaps the >> tracing >> or the

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On 12/03/18 21:20, Gedare Bloom wrote: Since I'm pretty keen on RTEMS, I think I'll have a 2nd proposal too, which I'll decide and discuss with you guys soon, hopefully! (Perhaps the tracing or the APA scheduling projects). That's fine. I don't think APA by itself is enough for the summer.

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 3:20 PM, Gedare Bloom wrote: > On Mon, Mar 12, 2018 at 12:41 PM, Amaan Cheval > wrote: > > On Mon, Mar 12, 2018 at 9:53 PM Gedare Bloom wrote: > > > >> On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber > >> wrote: > >> > On 10/03/18 18:02, Amaan Cheval wrote: > >> >> > >

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 12:41 PM, Amaan Cheval wrote: > On Mon, Mar 12, 2018 at 9:53 PM Gedare Bloom wrote: > >> On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber >> wrote: >> > On 10/03/18 18:02, Amaan Cheval wrote: >> >> >> >> - Improve RTEMS SMP[3] >> >> >> >> What kinds of improvements to SMP

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 9:53 PM Gedare Bloom wrote: > On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber > wrote: > > On 10/03/18 18:02, Amaan Cheval wrote: > >> > >> - Improve RTEMS SMP[3] > >> > >> What kinds of improvements to SMP are we considering? > > > > > > The SMP support is quite complet

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On Mon, Mar 12, 2018 at 3:01 AM, Sebastian Huber wrote: > On 10/03/18 18:02, Amaan Cheval wrote: >> >> - Improve RTEMS SMP[3] >> >> What kinds of improvements to SMP are we considering? > > > The SMP support is quite complete now. In general, an independent review is > required, but this is probab

Re: GSoC 2018 (x86_64, pc386, SMP improvements, rump kernels)

On 10/03/18 18:02, Amaan Cheval wrote: - Improve RTEMS SMP[3] What kinds of improvements to SMP are we considering? The SMP support is quite complete now. In general, an independent review is required, but this is probably not a GSoC project. Some areas in the implementation are a bit too co

Re: Gsoc 2018

See also Aditya's comments in "Re: devel Digest, Vol 76, Issue 23" On Fri, Mar 9, 2018 at 4:16 PM, Joel Sherrill wrote: > I just pushed a pretty significant update to the POSIX Compliance guide. > > + preface has more guidance on where to look for missing methods to > implement > + standards sect

Re: Gsoc 2018

I just pushed a pretty significant update to the POSIX Compliance guide. + preface has more guidance on where to look for missing methods to implement + standards section attempts to describe each standard. If this section is insufficient, patches or suggestions are encouraged. + Added C11 + Ad

Re: Gsoc 2018

On Thu, Mar 8, 2018 at 1:27 PM, Salil Sirotia wrote: > > Hello Developers, > > This is Salil Sirotia, Doing Masters from Indian Institute of > Technology, Dhanbad. I want to participate in GSoC 2018 at your > organization. > Hi.. I assume you have been talking to Aditya. :) > > > I have gone

Re: GSoC 2018 (was: Re: devel Digest, Vol 75, Issue 41)

ards Christian Mauderer > > Message: 1 > Date: Thu, 22 Feb 2018 15:48:52 +0100 > From: Christian Mauderer <mailto:christian.maude...@embedded-brains.de>> > To: devel@rtems.org <mailto:devel@rtems.org> > Subject: Re: GSOC 2018 > Message-ID: &

Re: GSOC 2018

Am 22.02.2018 um 03:35 schrieb Salil Sirotia: > Hi all, > > My name is Salil Sirotia and I'd like to be a part of RTEMS project for GSoC > 2018. > > As of now, I have gone through 'Getting Started documentation' > available on the devel.rteme.org  and have > managed to se

Re: GSoC 2018 Candidate (Patch and screenshot for hello world example)

On Wed, Jan 10, 2018 at 10:19 AM, Anshuman Chhabra wrote: > Respected Mentors, > > I am a final year electrical engineering student at the University of Delhi, > India. My resume is present here and my GitHub handle is anshuman23. I am > very interested in contributing to RTEMS over the summer as