<div dir="ltr"><div>Hi Christian,</div><div><br></div><div>I created a patch (attached in the mail) for review, which has CAN support.</div><div><br></div><div>Shall I send the patch for review to <a class="gmail_plusreply" id="plusReplyChip-0" href="mailto:devel@rtems.org" tabindex="-1">@rtems-devel@rtems.org</a>?</div><div><br></div><div>Regards</div><div>Prashanth S<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 11 Jul 2022 at 10:03, Prashanth S <<a href="mailto:fishesprashanth@gmail.com">fishesprashanth@gmail.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"><div dir="ltr"><div dir="auto">Hi Christian, <div dir="auto"><br></div><div dir="auto">This is to update the status. </div><div dir="auto"><br></div><div dir="auto">Yesterday, pushed a fix for a bug in tx path and added minimal rx path. </div><div dir="auto"><br></div><div dir="auto">Regards</div><div dir="auto">Prashanth S</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 7 Jul, 2022, 10:58 am Prashanth S, <<a href="mailto:fishesprashanth@gmail.com" target="_blank">fishesprashanth@gmail.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"><div dir="ltr"><div>Hi Gedare,</div><div><br></div><div>This is to ask for the License on the TI files.</div><div><br></div><div>As we already confirmed on the license for TI files as BSD, this is to double check.<br></div><div><br></div><div>I found two different licenses, I have added both of them.</div><div><br></div><div><b><font size="4">dcan.c and all header files (except dcan_frame.h)<br></font></b></div><div>/**<br> * \file dcan.c<br> *<br> * \brief DCAN APIs.<br> *<br> * This file contains the device abstraction layer APIs for <br> * Dual Controller Area Network(DCAN).<br> */<br><br>/*<br>* Copyright (C) 2010 Texas Instruments Incorporated - <a href="http://www.ti.com/" rel="noreferrer" target="_blank">http://www.ti.com/</a><br>*/<br>/*<br>* Redistribution and use in source and binary forms, with or without<br>* modification, are permitted provided that the following conditions<br>* are met:<br>*<br>* Redistributions of source code must retain the above copyright<br>* notice, this list of conditions and the following disclaimer.<br>*<br>* Redistributions in binary form must reproduce the above copyright<br>* notice, this list of conditions and the following disclaimer in the<br>* documentation and/or other materials provided with the<br>* distribution.<br>*<br>* Neither the name of Texas Instruments Incorporated nor the names of<br>* its contributors may be used to endorse or promote products derived<br>* from this software without specific prior written permission.<br>*<br>* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS<br>* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT<br>* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR<br>* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT<br>* OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,<br>* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT<br>* LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,<br>* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY<br>* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT<br>* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE<br>* OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<br>*<br>*/<br></div><div><div><br></div><div><font size="4"><b>dcan_frame.c and dcan_frame.h<br></b></font></div><div> * \file dcan_frame.c<br> *<br> * \brief This file consists of wrapper functions which internally call <br> * DCAN APIs.<br> */<br><br>/*<br> * Copyright (C) 2005 Marc Kleine-Budde, Pengutronix<br> * Copyright (C) 2006 Andrey Volkov, Varma Electronics<br> * Copyright (C) 2008-2009 Wolfgang Grandegger <<a href="mailto:wg@grandegger.com" rel="noreferrer" target="_blank">wg@grandegger.com</a>><br> *<br> * This program is free software; you can redistribute it and/or modify<br> * it under the terms of the version 2 of the GNU General Public License<br> * as published by the Free Software Foundation<br> *<br> * This program is distributed in the hope that it will be useful,<br> * but WITHOUT ANY WARRANTY; without even the implied warranty of<br> * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br> * GNU General Public License for more details.<br> *<br> * You should have received a copy of the GNU General Public License<br> * along with this program; if not, write to the Free Software<br> * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br> */<br></div><div><br></div></div><div>Regards</div><div>Prashanth S</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 1 Jun 2022 at 07:15, Gedare Bloom <<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</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">On Sun, May 29, 2022 at 6:09 AM Prashanth S <<a href="mailto:fishesprashanth@gmail.com" rel="noreferrer" target="_blank">fishesprashanth@gmail.com</a>> wrote:<br>
><br>
> Hi Christian,<br>
><br>
> Please make sure to take notes for blog posts or the weekly<br>
> status meeting.<br>
> Ok.<br>
><br>
> The License mentined in drivers/dcan.c<br>
><br>
> /*<br>
> * Copyright (C) 2010 Texas Instruments Incorporated - <a href="http://www.ti.com/" rel="noreferrer noreferrer" target="_blank">http://www.ti.com/</a><br>
> */<br>
> /*<br>
> * Redistribution and use in source and binary forms, with or without<br>
> * modification, are permitted provided that the following conditions<br>
> * are met:<br>
> *<br>
> * Redistributions of source code must retain the above copyright<br>
> * notice, this list of conditions and the following disclaimer.<br>
> *<br>
> * Redistributions in binary form must reproduce the above copyright<br>
> * notice, this list of conditions and the following disclaimer in the<br>
> * documentation and/or other materials provided with the<br>
> * distribution.<br>
> *<br>
> * Neither the name of Texas Instruments Incorporated nor the names of<br>
> * its contributors may be used to endorse or promote products derived<br>
> * from this software without specific prior written permission.<br>
> *<br>
> * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS<br>
> * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT<br>
> * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR<br>
> * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT<br>
> * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,<br>
> * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT<br>
> * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,<br>
> * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY<br>
> * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT<br>
> * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE<br>
> * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<br>
> *<br>
> */<br>
><br>
That license looks ok. It is a 3-BSD (2-BSD with advertising restriction).<br>
<br>
Is there an AM335x API for CAN in addition to the drivers? I have used<br>
TI's Tivaware before which has it's own CAN API, for example. That<br>
could be another possibility to consider for an initial simple target,<br>
if the code already exists for it.<br>
<br>
I think the choice of CAN API is a bit complicated. The grlib/grcan is<br>
actually a good choice for RTEMS.<br>
<br>
> Regards<br>
> Prashanth S<br>
><br>
> On Sun, 29 May 2022 at 13:33, Christian Mauderer <<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>> wrote:<br>
>><br>
>> Hello Prashanth,<br>
>><br>
>> sounds good. Please make sure to take notes for blog posts or the weekly<br>
>> status meeting.<br>
>><br>
>> You mention "Am335x starterware". Which license does that have? If it is<br>
>> compatible to the BSD license, it might would be possible to just port<br>
>> the driver.<br>
>><br>
>> Best regards<br>
>><br>
>> Christian<br>
>><br>
>> Am 28.05.22 um 16:15 schrieb Prashanth S:<br>
>> > Hi All,<br>
>> ><br>
>> > This is a status update on today's work.<br>
>> ><br>
>> > Gone through the HW initialization requirements for CAN loopback to work<br>
>> > in interrupt mode from Am335x starterware.<br>
>> > With this and the Am335x reference manual, I would try to understand the<br>
>> > HW initialization sequence and then start implementing the driver in RTEMS.<br>
>> ><br>
>> > Regards<br>
>> > Prashanth S<br>
>> ><br>
>> > On Fri, 27 May 2022 at 00:00, Christian Mauderer <<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>> wrote:<br>
>> ><br>
>> > Am 26.05.22 um 19:16 schrieb Prashanth S:<br>
>> > > Hi Christian,<br>
>> > ><br>
>> > > You have a medium sized project. That means it's no full time. Do<br>
>> > > you plan to work full time on the start or the end or part time<br>
>> > during<br>
>> > > the whole GSoC time?<br>
>> > > I plan to work part time on the weekdays and full time on the<br>
>> > weekends.<br>
>> > ><br>
>> > > The plan of project is more or less your proposal, isn't it?<br>
>> > > Yes the plan is the same as the proposal.<br>
>> > ><br>
>> > > Beneath that: I think you need a decision soon which CAN stack<br>
>> > you want<br>
>> > > to use. It will define some of the interfaces for the CAN driver.<br>
>> > Pavel<br>
>> > > suggested a few on the mailing list. I'm not sure whether there<br>
>> > was some<br>
>> > > final one selected?<br>
>> > > The final one is not selected yet. Meanwhile, I thought of<br>
>> > implementing<br>
>> > > the CAN driver<br>
>> > > and get the tx and rx working, and get the driver into the framework.<br>
>> ><br>
>> > You can start working on some parts but note that different driver<br>
>> > stacks can have quite different APIs. Therefore most of the time it's<br>
>> > simpler if you know the stack that should be used.<br>
>> ><br>
>> > ><br>
>> > > @<a href="mailto:pisa@cmp.felk.cvut.cz" rel="noreferrer" target="_blank">pisa@cmp.felk.cvut.cz</a> <mailto:<a href="mailto:pisa@cmp.felk.cvut.cz" rel="noreferrer" target="_blank">pisa@cmp.felk.cvut.cz</a>><br>
>> > <mailto:<a href="mailto:pisa@cmp.felk.cvut.cz" rel="noreferrer" target="_blank">pisa@cmp.felk.cvut.cz</a> <mailto:<a href="mailto:pisa@cmp.felk.cvut.cz" rel="noreferrer" target="_blank">pisa@cmp.felk.cvut.cz</a>>> ,<br>
>> > @Christian<br>
>> > > Mauderer <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>> ,<br>
>> > @Gedare Bloom<br>
>> > > <mailto:<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</a> <mailto:<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</a>>> .<br>
>> > ><br>
>> > > May I ask for suggestions on the CAN framework for RTEMS.<br>
>> > > Shall I take the suggested stacks as reference and develop APIs<br>
>> > and data<br>
>> > > structures.<br>
>> > > Or select a particular stack and port the required features?<br>
>> ><br>
>> > I think Pavel knows CAN stacks and frameworks a lot better than me.<br>
>> > So I<br>
>> > hope that he can suggest a good approach here.<br>
>> ><br>
>> > I think the discussion on the list about the stacks stopped about a<br>
>> > month ago without a result, did it? The last mail seems to be from<br>
>> > Pavel<br>
>> > from 16.04.. He suggested some directions. Maybe you can create a plan<br>
>> > based on that and post it to the list for further discussions.<br>
>> ><br>
>> > It would be good to do that soon so that the discussion can take place<br>
>> > while you are still doing other things like setting up your hardware<br>
>> > and<br>
>> > the Linux test setup.<br>
>> ><br>
>> > ><br>
>> > > Is a JTAG setup for BBB needed or prints would be sufficient for<br>
>> > debugging?<br>
>> ><br>
>> > Having a good debug solution is always useful in my experience. So if<br>
>> > you have the possibility to set up a JTAG debugger, you should invest<br>
>> > the time. Using prints could work in this project but it is<br>
>> > definitively<br>
>> > a inferior solution. Another possibility in this case could be<br>
>> > libdebugger. But I have to say that I never used that myself because I<br>
>> > always had a hardware debugger.<br>
>> ><br>
>> > Best regards<br>
>> ><br>
>> > Christian<br>
>> ><br>
>> > ><br>
>> > ><br>
>> > > Regards<br>
>> > > Prashanth S<br>
>> > ><br>
>> > ><br>
>> > > On Thu, 26 May 2022 at 21:33, Christian Mauderer<br>
>> > <<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>>> wrote:<br>
>> > ><br>
>> > > Hello Prashanth,<br>
>> > ><br>
>> > > Am 26.05.22 um 17:40 schrieb Prashanth S:<br>
>> > > > Hi Christian Mauderer,<br>
>> > > ><br>
>> > > > Thank You.<br>
>> > > ><br>
>> > > > Most of the time the RTEMS mailing list is quite informal and<br>
>> > > most of us<br>
>> > > > just use first names to address someone ("Christian" in my<br>
>> > case). Is<br>
>> > > > that OK for you too? How do you prefer to be addressed?<br>
>> > > > Yes, no problem in calling me by first name (Prashanth).<br>
>> > > ><br>
>> > > > Last years it always was a good idea to sort out time<br>
>> > zones. You<br>
>> > > > mentioned that you are from India so you are most likely at<br>
>> > > UTC+5:30? Is<br>
>> > > > that correct? I'm in Germany and therefore my time is UTC+2<br>
>> > > during the<br>
>> > > > summer. That means that I sometimes forget at my evening<br>
>> > that's<br>
>> > > already<br>
>> > > > late in the night for you. Please don't hesitate to just<br>
>> > tell me<br>
>> > > that we<br>
>> > > > should continue a discussion on the next day if it starts<br>
>> > to get too<br>
>> > > > late for you ;-)<br>
>> > > > Yes, my time zone is UTC +5:30.<br>
>> > > ><br>
>> > > > Do you already have everything set up or do you<br>
>> > > > need some help with that? Maybe you can tell me roughly<br>
>> > what hardware<br>
>> > > > you use? I would like to try to reproduce the setup here<br>
>> > so that<br>
>> > > I can<br>
>> > > > test your software or help with debugging where necessary.<br>
>> > > > I have a BBB and Sn65Hvd230 Can Bus Transceiver. I am<br>
>> > planning to<br>
>> > > buy<br>
>> > > > one more<br>
>> > > > BBB for testing CAN driver.<br>
>> > > ><br>
>> > > > @<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>><br>
>> > > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>>> , @Pavel Pisa<br>
>> > > > <mailto:<a href="mailto:ppisa4lists@pikron.com" rel="noreferrer" target="_blank">ppisa4lists@pikron.com</a><br>
>> > <mailto:<a href="mailto:ppisa4lists@pikron.com" rel="noreferrer" target="_blank">ppisa4lists@pikron.com</a>> <mailto:<a href="mailto:ppisa4lists@pikron.com" rel="noreferrer" target="_blank">ppisa4lists@pikron.com</a><br>
>> > <mailto:<a href="mailto:ppisa4lists@pikron.com" rel="noreferrer" target="_blank">ppisa4lists@pikron.com</a>>>> ,<br>
>> > > @Gedare Bloom <mailto:<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</a><br>
>> > <mailto:<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</a>> <mailto:<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</a><br>
>> > <mailto:<a href="mailto:gedare@rtems.org" rel="noreferrer" target="_blank">gedare@rtems.org</a>>>> .<br>
>> > > ><br>
>> > > > How do you prefer to be addressed?<br>
>> > ><br>
>> > > Like I said: First name is OK. So just Christian.<br>
>> > ><br>
>> > > ><br>
>> > > > I would like to start the programming part early.<br>
>> > ><br>
>> > > OK. You have a medium sized project. That means it's no full<br>
>> > time. Do<br>
>> > > you plan to work full time on the start or the end or part<br>
>> > time during<br>
>> > > the whole GSoC time?<br>
>> > ><br>
>> > > ><br>
>> > > > May I ask, what are the things I need to do before starting?<br>
>> > > > (Like, plan of the project, module design, creating a github<br>
>> > > repo, blog<br>
>> > > > posts)<br>
>> > ><br>
>> > > The plan of project is more or less your proposal, isn't it?<br>
>> > ><br>
>> > > I would suggest to start with a blog early. It's nice if you<br>
>> > create it<br>
>> > > more or less as a "diary" what you did. It maybe isn't a bad<br>
>> > idea to<br>
>> > > plan for example about weekly posts as a preparation for the<br>
>> > > meetings on<br>
>> > > Discord. But you can also do posts every time you have a nice<br>
>> > > self-contained part of work or similar.<br>
>> > ><br>
>> > > I think you planned to test your hardware setup with Linux.<br>
>> > So maybe a<br>
>> > > nice first post could be about your hardware setup and how it<br>
>> > runs the<br>
>> > > Linux sample.<br>
>> > ><br>
>> > > Beneath that: I think you need a decision soon which CAN<br>
>> > stack you want<br>
>> > > to use. It will define some of the interfaces for the CAN<br>
>> > driver. Pavel<br>
>> > > suggested a few on the mailing list. I'm not sure whether<br>
>> > there was<br>
>> > > some<br>
>> > > final one selected?<br>
>> > ><br>
>> > ><br>
>> > > Setting up a GitHub Repo is also a good idea but you need<br>
>> > something<br>
>> > > that<br>
>> > > you want to put there. Only cloning the RTEMS repo isn't<br>
>> > really useful<br>
>> > > if you don't add patches.<br>
>> > ><br>
>> > > I tend to keep my working environment in a repository. If you<br>
>> > want to<br>
>> > > use something like that, this might be a good starting point<br>
>> > for a<br>
>> > > repository. Basically just some commands in scripts and makefiles<br>
>> > > together with demo applications and repositories pulled in as<br>
>> > > submodules. That makes it simple to reproduce a certain<br>
>> > version. I<br>
>> > > would<br>
>> > > strongly suggest to create it yourself because then you know<br>
>> > your way<br>
>> > > around it. But if you want, you can also take a look at what<br>
>> > I use<br>
>> > > since<br>
>> > > some years for testing code from BBB-GSoC projects:<br>
>> > ><br>
>> > > <a href="https://gitlab.com/c-mauderer/rtems-bbb" rel="noreferrer noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-bbb</a><br>
>> > <<a href="https://gitlab.com/c-mauderer/rtems-bbb" rel="noreferrer noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-bbb</a>><br>
>> > > <<a href="https://gitlab.com/c-mauderer/rtems-bbb" rel="noreferrer noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-bbb</a><br>
>> > <<a href="https://gitlab.com/c-mauderer/rtems-bbb" rel="noreferrer noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-bbb</a>>><br>
>> > ><br>
>> > > But like I said: Please think about starting something like<br>
>> > that from<br>
>> > > scratch because you then know every line of it and where you<br>
>> > have to<br>
>> > > change something.<br>
>> > ><br>
>> > > Best regards<br>
>> > ><br>
>> > > Christian<br>
>> > ><br>
>> > > ><br>
>> > > > Regards<br>
>> > > > Prashanth S<br>
>> > > ><br>
>> > > > On Thu, 26 May 2022 at 20:24, Christian Mauderer<br>
>> > > <<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>><br>
>> > > > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>>>> wrote:<br>
>> > > ><br>
>> > > ><br>
>> > > > Hello Prashanth S,<br>
>> > > ><br>
>> > > > welcome to this years GSoC.<br>
>> > > ><br>
>> > > > I'm sure you have already seen that Pavel and I have been<br>
>> > > assigned as<br>
>> > > > mentor to your project. Gedare is backup in case one<br>
>> > or both<br>
>> > > of us are<br>
>> > > > unavailable for some reason (which normally shouldn't<br>
>> > be the<br>
>> > > case).<br>
>> > > ><br>
>> > > > Gedare already mentioned it in yesterdays meeting: We<br>
>> > should<br>
>> > > try to<br>
>> > > > communicate often. Don't hesitate to ask many questions if<br>
>> > > you get<br>
>> > > > stuck. Don't worry whether a question might be to<br>
>> > "easy". Asking<br>
>> > > > them is<br>
>> > > > the best way to learn the answer. Beneath that it<br>
>> > helps me to<br>
>> > > keep<br>
>> > > > up to<br>
>> > > > date what are you doing and that makes it simpler to<br>
>> > help you.<br>
>> > > ><br>
>> > > ><br>
>> > > > Most of the time the RTEMS mailing list is quite<br>
>> > informal and<br>
>> > > most<br>
>> > > > of us<br>
>> > > > just use first names to address someone ("Christian" in my<br>
>> > > case). Is<br>
>> > > > that OK for you too? How do you prefer to be addressed?<br>
>> > > ><br>
>> > > ><br>
>> > > > We should try to find some common communication<br>
>> > methods. In<br>
>> > > the best<br>
>> > > > case you use public channels like the mailing list or<br>
>> > the public<br>
>> > > > Discord<br>
>> > > > chat. But I know that it's sometimes a bit difficult<br>
>> > to use<br>
>> > > these if<br>
>> > > > you<br>
>> > > > are new to open source projects. I still know how<br>
>> > nervous I<br>
>> > > have been<br>
>> > > > when I wrote my first mails to the list. So if you<br>
>> > have some<br>
>> > > topics<br>
>> > > > that<br>
>> > > > you prefere to discuss private, you can always reach us by<br>
>> > > mail or<br>
>> > > > private chat.<br>
>> > > ><br>
>> > > > I think Pavel isn't on Discord (Pavel: please correct<br>
>> > me if<br>
>> > > I'm wrong).<br>
>> > > > Discord isn't really known for their privacy friendly<br>
>> > > attitude so I can<br>
>> > > > completely understand that. So at the moment the best<br>
>> > method<br>
>> > > to reach<br>
>> > > > all of us is most likely mail.<br>
>> > > ><br>
>> > > > My private mail address that I use for open source<br>
>> > work is the<br>
>> > > > <<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>><br>
>> > > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>><br>
>> > <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a> <mailto:<a href="mailto:oss@c-mauderer.de" rel="noreferrer" target="_blank">oss@c-mauderer.de</a>>>>>. I check<br>
>> > > these mails<br>
>> > > > at least once a day (most of<br>
>> > > > the time more often). If you have something that has to be<br>
>> > > answered<br>
>> > > > really fast, you might want to add my company mail address<br>
>> > > > <<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a><br>
>> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
>> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a><br>
>> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
>> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a><br>
>> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
>> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a><br>
>> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" rel="noreferrer" target="_blank">christian.mauderer@embedded-brains.de</a>>>>> to CC. You will find<br>
>> > > > these two<br>
>> > > > addresses on the mailing list too.<br>
>> > > ><br>
>> > > > Note that I have a mail filter that sorts mails from<br>
>> > the list<br>
>> > > into<br>
>> > > > folders. If you want to make sure that I read a mail<br>
>> > on the<br>
>> > > list: Add<br>
>> > > > one of my addresses to CC so that my filter keeps it<br>
>> > in the<br>
>> > > inbox.<br>
>> > > > That's a good idea for most people on the list: If you<br>
>> > want<br>
>> > > someone<br>
>> > > > special to answer something: Add him or her to CC. But<br>
>> > please<br>
>> > > make sure<br>
>> > > > that you only add addresses to CC that are already used in<br>
>> > > public.<br>
>> > > ><br>
>> > > ><br>
>> > > > Last years it always was a good idea to sort out time<br>
>> > zones. You<br>
>> > > > mentioned that you are from India so you are most<br>
>> > likely at<br>
>> > > > UTC+5:30? Is<br>
>> > > > that correct? I'm in Germany and therefore my time is<br>
>> > UTC+2<br>
>> > > during the<br>
>> > > > summer. That means that I sometimes forget at my evening<br>
>> > > that's already<br>
>> > > > late in the night for you. Please don't hesitate to<br>
>> > just tell me<br>
>> > > > that we<br>
>> > > > should continue a discussion on the next day if it<br>
>> > starts to<br>
>> > > get too<br>
>> > > > late for you ;-)<br>
>> > > ><br>
>> > > > I'm not entirely sure which time zones Pavel and<br>
>> > Gedare have<br>
>> > > but I'm<br>
>> > > > sure you will find out soon enough when you can reach<br>
>> > every<br>
>> > > one of them.<br>
>> > > ><br>
>> > > ><br>
>> > > > I think that's enough general information for the moment.<br>
>> > > Let's start a<br>
>> > > > (short) technical part:<br>
>> > > ><br>
>> > > > I have to be honest: I haven't followed every mail on<br>
>> > the list<br>
>> > > > regarding<br>
>> > > > your project during the last weeks. So maybe let me<br>
>> > ask a bit<br>
>> > > about<br>
>> > > > your<br>
>> > > > current hardware setup: Do you already have everything<br>
>> > set up<br>
>> > > or do you<br>
>> > > > need some help with that? Maybe you can tell me<br>
>> > roughly what<br>
>> > > hardware<br>
>> > > > you use? I would like to try to reproduce the setup<br>
>> > here so<br>
>> > > that I can<br>
>> > > > test your software or help with debugging where necessary.<br>
>> > > ><br>
>> > > > Best regards<br>
>> > > ><br>
>> > > > Christian<br>
>> > > ><br>
>> > ><br>
>> ><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>