<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Dec 30, 2019 at 4:44 AM Peter Dufault <<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Niteesh, what do you want to study? Go over what most interests you most about working in a real-time environment like RTEMS, and not about working on the RPI, and look at the earlier GSOC projects. Propose an ideal project for yourself and get some feedback.</blockquote><div> I love learning about how the software and hardware interact, I have been programming from 9th grade and have a wide variety of interests(networking, app development). But recently I took a course called nandtotetris were we build an 8bit computer from scratch, we start with NAND gates and finally finish with a Tetris game. Low-level software, systems programming, and operating systems are always quite fascinating for me. While learning about operating systems, I came across the concepts of real-time systems. Back then arduino was the only hardware I was having while searching for an RTOS to play with, I came across RTEMS. RTOS was harder for me to grasp but were always interesting, being a critical part of a system, I always wanted to learn how they worked from inside. That's what bought me to contributing to RTOS.</div><div>I wanted to contribute to core of RTEMS, but it was a bit complex for me to understand, so I started with driver development for RTEMS. </div><div>After going through some of the previous GSOC projects, BSP development and real-time tracing are what I find interesting. While also converting the console driver of rpi to FDT based one, <b>Christian Mauderer </b>explained how </div><div>FDT worked in FreeBSD and Linux, and RTEMS lacked that infrastructure, I have no idea of how hard it would it, and if I am even capable of developing it. But one proposal would be to build the FDT infrastructure similar to FreeBSD or Linux and have the driver's probe and attach to the hardware.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> On Dec 28, 2019, at 05:12 , Christian Mauderer <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>> wrote:<br>
> <br>
> On 28/12/2019 07:12, Niteesh wrote:<br>
>> <br>
>> <br>
>> On Sat, 28 Dec, 2019, 3:51 AM Christian Mauderer, <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a><br>
>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>> wrote:<br>
>> <br>
>> On 27/12/2019 19:06, Niteesh wrote:<br>
>>> Is there something else that I could work on? I am interested in<br>
>> taking<br>
>>> part <br>
>>> GSOC of 2020. And I want to learn as much as possible.<br>
>> <br>
>> Do you search tasks specific to raspberry or general ones? Do you search<br>
>> something for GSoC or just to warm up?<br>
>> <br>
>> Anything is fine as long as I am learning something. Since rpi3 is the<br>
>> only hardware I have, I am interested in tasks specific to raspi and<br>
>> general ones which do not require any hardware.<br>
> <br>
> For raspberry I think you could continue to get it running on RPi3. My<br>
> suggestion would be to replace the table based initialization (which is<br>
> handled by console-termios-init.c) with one based on the fdt that is<br>
> similar to the one in the imx BSP. That will allow to use the same<br>
> binary on RPi2 and RPi3. But please do that in an extra patch after the<br>
> one that you currently have sent to the mailing list.<br>
> <br>
> <br>
> Some other raspberry specific topics could be the following. Note that<br>
> this are only suggestions. I don't want to force you to do any of them<br>
> if you don't like them:<br>
> <br>
> - Documentation how you run an application in QEMU / on real hardware<br>
> for the user manual:<br>
> <a href="https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#raspberrypi" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#raspberrypi</a><br>
> (I hope I didn't miss a patch that you already sent ;-) )<br>
> <br>
> - A configuration for RTEMS tester that uses the QEMU or real hardware<br>
> (I think the pi3 allows network boot?). This allows regular test runs<br>
> for this BSP:<br>
> <a href="https://docs.rtems.org/branches/master/user/testing/index.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/testing/index.html</a> and<br>
> <a href="https://docs.rtems.org/branches/master/user/tools/tester.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/tools/tester.html</a><br>
> <br>
> - Chris created a boot image generator last year. It would be great if<br>
> you could add a configuration to create raspberry SD images to it:<br>
> <a href="https://docs.rtems.org/branches/master/user/tools/boot-image.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/tools/boot-image.html</a><br>
> <br>
> - You can pick basically any component that isn't already there and<br>
> integrate it. If you want to work with libbsd: Testing or porting<br>
> Ethernet support could be something.<br>
> <br>
> - You most likely want to do something with RPi in your GSoC too. So<br>
> maybe some comments ("x is already done", "y seems to be still open")<br>
> for the ticket for it would be nice too: <a href="https://devel.rtems.org/ticket/2899" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2899</a><br>
> <br>
> <br>
> For non raspberry topics: We have a lot of open bugs where everyone is<br>
> happy if they are closed: <a href="https://devel.rtems.org/query" rel="noreferrer" target="_blank">https://devel.rtems.org/query</a><br>
> <br>
> A lot of them might are even out of date and just need someone who reads<br>
> them and asks whether they can be closed.<br>
> <br>
>> <br>
>> <br>
>>> <br>
>>> On Fri, Dec 27, 2019 at 5:07 PM Christian Mauderer<br>
>> <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>><br>
>>> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a> <mailto:<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>>>> wrote:<br>
>>> <br>
>>> On 27/12/2019 12:20, Niteesh wrote:<br>
>>> > I have sent the patch. I also sent a documentation update<br>
>> for the<br>
>>> > quick-start section<br>
>>> > a few months ago. But no one took a look at it. Can you have a<br>
>>> look at it?<br>
>>> <br>
>>> I'll try to have a look at it soon.<br>
>>> <br>
>>> ><br>
>>> > <a href="https://www.mail-archive.com/devel@rtems.org/msg20965.html" rel="noreferrer" target="_blank">https://www.mail-archive.com/devel@rtems.org/msg20965.html</a><br>
>>> <br>
>>> If you don't get any responses to a patch please just send a<br>
>> reminder<br>
>>> one or two weeks later. It's quite likely that the patch just<br>
>> slipped<br>
>>> the attention.<br>
>>> <br>
>>> Normally I leave documentation patches to our native speakers.<br>
>> They spot<br>
>>> a lot of errors that I won't be able to find.<br>
>>> <br>
>>> Can you please send a ping for the patch. You can add me to CC<br>
>> and for<br>
>>> this one I would suggest to CC Chris Johns too.<br>
>>> <br>
>> <br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
<br>
Peter<br>
-----------------<br>
Peter Dufault<br>
HD Associates, Inc. Software and System Engineering<br>
<br>
This email is delivered through the public internet using protocols subject to interception and tampering.<br>
<br>
</blockquote></div></div>