<div dir="ltr"><div dir="ltr">On Fri, Jan 3, 2020 at 7:30 PM Christian Mauderer <<a href="mailto:list@c-mauderer.de" target="_blank">list@c-mauderer.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 03/01/2020 13:49, Niteesh wrote:<br>
> I have gone through previous year works and selected a few topics which<br>
> I found<br>
> interesting.<br>
> 1. Basic Support for Trace Compass #3696<br>
> <<a href="https://devel.rtems.org/ticket/3696" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3696</a>>.<br>
<br>
A basic support has been added last year and Sebastian extended that<br>
quite a bit because we had a customer who needed it. I'm not sure what<br>
the current state is and whether there are tasks left that could be done<br>
in a GSoC project.<br>
<br>
> 2. RTEMS testing tool project #2927 <<a href="https://devel.rtems.org/ticket/2927" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2927</a>>.<br>
<br>
No idea what the status is. Chris?<br>
<br>
> 3. Beagle BSP: Add a flattened device tree based initialization #3784<br>
> <<a href="https://devel.rtems.org/ticket/3784" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3784</a>>.<br>
<br>
That one is open. It would include adding some infrastructure for fdt<br>
based drivers. In theory you could do the same project for raspberry or<br>
any other board.<br>
<br>
Please note Gedares comment from the previous mail:<br>
<br>
> Infrastructure projects are nice (FDT, dynamic linking, debugger,<br>
> tracer) but need to be clearly defined ahead of time and discussed<br>
> thoroughly with the community, or you risk ending up in the "long<br>
> tedious discussions" when you should be coding.<br>
<br>
<br>
> 4. BSPs for Simulators #2903 <<a href="https://devel.rtems.org/ticket/2903" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2903</a>>.<br>
<br>
That's always open.<br>
<br>
Some simulators are easy because the board is already supported and you<br>
only have to find out how to start it. For these a tester integration is<br>
a good target. But most likely that's only small stuff and should be<br>
only one part of a project.<br>
<br>
Other simulators are not supported yet. In that case you have to write<br>
some drivers which can be a good project size.<br>
<br>
> 5. Improve the Raspberry Pi BSP #2899 <<a href="https://devel.rtems.org/ticket/2899" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2899</a>>.<br>
<br>
You already noted: The raspberry BSP isn't in the best shape. So it's<br>
quite open for improvement.<br>
<br>
I think that there is still some work getting it to run again. We don't<br>
have something with "*bcm*" in libbsd yet so most likely USB and<br>
Ethernet are not working yet. Could be still still be a nice task.<br></blockquote><div><br></div><div>Why don't we use the driver's from other sources as a reference and create our</div><div>own, for USB <a href="https://github.com/Chadderz121/csud" target="_blank">https://github.com/Chadderz121/csud</a> this could be used as a</div><div>reference, U-boot, and Linux are good sources too. But is it worth the effort for a</div><div>BSP like raspberry pi? There is also a c++ bare metal environment called circle</div><div><a href="https://github.com/rsta2/circle" target="_blank">https://github.com/rsta2/circle</a> which supports USB(<a href="https://github.com/rsta2/uspi" target="_blank">https://github.com/rsta2/uspi</a>)</div><div>and ethernet.</div><div><br></div><div>Christian, can you check out this <a href="https://github.com/0xabu/qemu/wiki" target="_blank">https://github.com/0xabu/qemu/wiki</a> it partially supports</div><div>USB, can you give it a try?</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
With the difficulties getting it to run on RPi3 or RPi4 that might could<br>
be also a project. It seems that they are aarch64. Also I was quite<br>
surprised about it I didn't find a aarch64 BSP. So that would be a new port.<br></blockquote><div> </div><div>Rpi3 looks for kernel7.img if it finds one, it boots into 32bit mode, so if the, offset is the only difference</div><div>between rpi2 and rpi3 it should boot without any issues I'll try adding the AUX uart driver</div><div>and see if it boots on Rpi3.</div><div><br></div><div>I would also like to discuss about the FDT infrastructure for RTEMS, I would like to know what are</div><div>the requirements, what could be expected in a short span of 3months, what could be used as a reference</div><div>and so on.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Note that an aarch64 port would most likely be observed with argus eyes<br>
because it has the potential to be a very important port. But don't let<br>
that keep you bag suggesting it.<br>
<br>
> <br>
> I would like to know what are the future plans for these topics.<br>
> What is the current status of USB and ethernet in raspberrypi?<br>
> Does the beagle BSP require hardware or is it possible to emulate it?<br>
<br>
I never used an emulator for Beagle. It seems that qemu supported it<br>
some when:<br>
<a href="https://www.cnx-software.com/2011/09/26/beagleboard-emulator-in-ubuntu-with-qemu/" rel="noreferrer" target="_blank">https://www.cnx-software.com/2011/09/26/beagleboard-emulator-in-ubuntu-with-qemu/</a><br>
<br>
But I didn't find it in current qemu. So most likely it would need hardware.<br>
<br>
> Last year Vijay Kumar Banerjee worked on analysis and generation of gcov<br>
> reports.<br>
> <br>
> On Thu, Jan 2, 2020 at 10:07 PM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a><br>
> <mailto:<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>>> wrote:<br>
> <br>
> On Mon, Dec 30, 2019 at 2:47 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>>> wrote:<br>
> ><br>
> > On 30/12/2019 15:45, Niteesh wrote:<br>
> > > On Mon, Dec 30, 2019 at 7:14 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 30/12/2019 07:25, Niteesh wrote:<br>
> > > ><br>
> > > ><br>
> > > > On Mon, Dec 30, 2019 at 4:44 AM Peter Dufault<br>
> <<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a> <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a>><br>
> > > <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a> <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a>>><br>
> > > > <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a> <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a>><br>
> <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a> <mailto:<a href="mailto:dufault@hda.com" target="_blank">dufault@hda.com</a>>>>> wrote:<br>
> > > ><br>
> > > ><br>
> > > > Niteesh, what do you want to study? Go over what most<br>
> > > interests you<br>
> > > > most about working in a real-time environment like<br>
> RTEMS, and not<br>
> > > > about working on the RPI, and look at the earlier GSOC<br>
> projects.<br>
> > > > Propose an ideal project for yourself and get some<br>
> feedback.<br>
> > ><br>
> > > Peter: Thanks for starting that discussion. I started to<br>
> focus too much<br>
> > > on the running topics about small stuff that can be done as a<br>
> > > preparation.<br>
> > ><br>
> > > ><br>
> > > > I love learning about how the software and hardware<br>
> interact, I have<br>
> > > > been programming from 9th grade and have a wide variety of<br>
> > > > interests(networking, app development). But recently I<br>
> took a course<br>
> > > > called nandtotetris were we build an 8bit computer from<br>
> scratch, we<br>
> > > > start with NAND gates and finally finish with a Tetris game.<br>
> > ><br>
> > > That sounds like a really nice course. Most likely is ended<br>
> in a bigger<br>
> > > pile of circuit boards to have a running processor ;-)<br>
> > ><br>
> > > It is a free course on<br>
> > > coursera<br>
> <a href="https://www.coursera.org/learn/build-a-computer/home/welcome" rel="noreferrer" target="_blank">https://www.coursera.org/learn/build-a-computer/home/welcome</a><br>
> > > do check it out. It's completely simulated in software. But<br>
> planning to<br>
> > > build it on PCB.<br>
> > ><br>
> > ><br>
> > > > Low-level<br>
> > > > software, systems programming, and operating systems are<br>
> always quite<br>
> > > > fascinating for me. While learning about operating<br>
> systems, I came<br>
> > > > across the concepts of real-time systems. Back then<br>
> arduino was<br>
> > > the only<br>
> > > > hardware I was having while searching for an RTOS to play<br>
> with, I came<br>
> > > > across RTEMS. RTOS was harder for me to grasp but were always<br>
> > > > interesting, being a critical part of a system, I always<br>
> wanted to<br>
> > > learn<br>
> > > > how they worked from inside. That's what bought me to<br>
> contributing<br>
> > > to RTOS.<br>
> > > > I wanted to contribute to core of RTEMS, but it was a bit<br>
> complex<br>
> > > for me<br>
> > > > to understand, so I started with driver development for RTEMS.<br>
> > ><br>
> > > That's where I started too. But don't hesitate to pick a<br>
> more complex<br>
> > > topic if you are interested in it. From what I've seen you<br>
> can read and<br>
> > > understand existing code quite fast compared to some other<br>
> GSoC students<br>
> > > we had. So I would say that you have a good chance to manage<br>
> complex<br>
> > > topics too.<br>
> > ><br>
> > > Thank you, it's quite good to hear.<br>
> > ><br>
> > > > After going through some of the previous GSOC projects, BSP<br>
> > > development<br>
> > > > and real-time tracing are what I find interesting. While also<br>
> > > converting<br>
> > > > the console driver of rpi to FDT based one, *Christian<br>
> Mauderer<br>
> > > > *explained how<br>
> > > > FDT worked in FreeBSD and Linux, and RTEMS lacked that<br>
> > > infrastructure, I<br>
> > > > have no idea of how hard it would it, and if I am even<br>
> capable of<br>
> > > > developing it. But one proposal would be to build the FDT<br>
> > > infrastructure<br>
> > > > similar to FreeBSD or Linux and have the driver's probe<br>
> and attach to<br>
> > > > the hardware.<br>
> > ><br>
> > > We start to have more and more FDT based BSPs. So it would<br>
> be great if<br>
> > > our infrastructure would improve. But like I said: Don't<br>
> hesitate to<br>
> > > pick any other topic. Device drivers (and similar) are low<br>
> hanging fruit<br>
> > > where it is easy to get success and it isn't very likely to<br>
> start long<br>
> > > tedious discussions because you only touch one BSP.<br>
> Therefore I tend to<br>
> > > suggest them for GSoC. But GSoC isn't limited to that.<br>
> > ><br>
> > > So if you would like to work at any other topic like (for<br>
> example)<br>
> > > porting a new architecture, hacking on some scheduler, do<br>
> something with<br>
> > > the dynamic linking support, add stuff to the libdebugger,<br>
> or basically<br>
> > > anything else: Just ask whether someone knows a topic in<br>
> that area or is<br>
> > > interested in mentoring one you suggest. Most likely the<br>
> mailing list<br>
> > > will become quite a bit more active again in about a week.<br>
> > ><br>
> I'll be lurking.<br>
> <br>
> Infrastructure projects are nice (FDT, dynamic linking, debugger,<br>
> tracer) but need to be clearly defined ahead of time and discussed<br>
> thoroughly with the community, or you risk ending up in the "long<br>
> tedious discussions" when you should be coding.<br>
> <br>
> BSP Projects are only good if they are useful. RPI3 might be useful,<br>
> although there haven't been a lot of folks clamoring for it.<br>
> <br>
> > > Once I finish with the raspberry pi, I will try to port RTEMS<br>
> for esp32.<br>
> > > I have that board,<br>
> > > It has quite a lot of features and really good documentation. It is<br>
> > > based on xtensa CPU.<br>
> > > <a href="https://devel.rtems.org/wiki/TBR/UserManual/SupportedCPUs" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/TBR/UserManual/SupportedCPUs</a> and is<br>
> under<br>
> > > RTEMS potential port.<br>
> > ><br>
> ><br>
> > Interesting idea. You should post that as a project idea for your GSoC<br>
> > project. There are quite some points for new cores that can make a<br>
> port<br>
> > very simple or hard as hell. I don't have the experience to give a<br>
> good<br>
> > estimate for that core. But don't worry. I'm quite sure that this<br>
> can be<br>
> > an interesting project.<br>
> ><br>
> > Just some random thoughts:<br>
> ><br>
> > - It seems that the Xtensa is supported in the official GCC since<br>
> quite<br>
> > some time up to the most recent releases. That's a really good<br>
> starting<br>
> > point.<br>
> ><br>
> > - The core is a commercial IP core. It might can get hard to get a<br>
> > detailed core documentation. Let's hope that there is enough community<br>
> > documentation for it.<br>
> ><br>
> > - I didn't really find the core in any other (buyable) chip but the<br>
> > ESP32. Do you know whether it is used somewhere else?<br>
> ><br>
> > - The ESP32 doesn't have too much RAM. If I've seen it right it's<br>
> 520kB<br>
> > on-chip. We have smaller targets than that but it's not really<br>
> much. The<br>
> > libbsd network stack will most likely never run on it. But lwIP should<br>
> > work. But I think network stack is something that won't be a topic<br>
> for a<br>
> > first port anyway ;-)<br>
> ><br>
> > - The Technical Reference Manual looks reasonable detailed:<br>
> ><br>
> <a href="https://docs.espressif.com/projects/esp-idf/en/latest/hw-reference/index.html" rel="noreferrer" target="_blank">https://docs.espressif.com/projects/esp-idf/en/latest/hw-reference/index.html</a><br>
> ><br>
> > - For the low level port you definitively need a hardware debugger<br>
> or a<br>
> > good simulator. It seems that JTAG access is possible using OpenOCD.<br>
> > There is even an official guide from the manufacturer:<br>
> ><br>
> <a href="https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/" rel="noreferrer" target="_blank">https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/</a><br>
> ><br>
> <br>
> A new architecture port is a worthwhile GSoC Project. There would be a<br>
> lot of learning and code generated. However as above there is a<br>
> question about utility: Will there be more than 1 xtensa user?<br>
> Historically, DPSs seem to have low demand for an RTOS like RTEMS. It<br>
> is still a good GSoC project though. One of the barriers to a new<br>
> architecture however will be testability: is there a simulator that<br>
> can be used for development/testing?<br>
> <br>
> For difficulty, the thing to investigate is how complex is the<br>
> register context, interrupt handling mechanisms, memory management,<br>
> and on-chip devices (timers, etc.). Also whether or not there is a<br>
> 2/3-BSD compliant port elsewhere for reusable code. The base xtensa<br>
> looks straightforward. The ESP32 is an interesting board.<br>
> <br>
> > ><br>
> > > ><br>
> > > > > On Dec 28, 2019, at 05:12 , 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>>><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>><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 28/12/2019 07:12, Niteesh wrote:<br>
> > > > >><br>
> > > > >><br>
> > > > >> On Sat, 28 Dec, 2019, 3:51 AM 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>>><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>><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>>>><br>
> > > > >> <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><br>
> <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>><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 19:06, Niteesh wrote:<br>
> > > > >>> Is there something else that I could work on? I am<br>
> > > 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<br>
> > > ones? Do<br>
> > > > you search<br>
> > > > >> something for GSoC or just to warm up?<br>
> > > > >><br>
> > > > >> Anything is fine as long as I am learning<br>
> something. Since rpi3<br>
> > > > is the<br>
> > > > >> only hardware I have, I am interested in tasks<br>
> specific to<br>
> > > raspi and<br>
> > > > >> general ones which do not require any hardware.<br>
> > > > ><br>
> > > > > For raspberry I think you could continue to get it<br>
> running<br>
> > > on RPi3. My<br>
> > > > > suggestion would be to replace the table based<br>
> initialization<br>
> > > > (which is<br>
> > > > > handled by console-termios-init.c) with one based on<br>
> the fdt<br>
> > > that is<br>
> > > > > similar to the one in the imx BSP. That will allow<br>
> to use<br>
> > > the same<br>
> > > > > binary on RPi2 and RPi3. But please do that in an<br>
> extra patch<br>
> > > > after the<br>
> > > > > one that you currently have sent to the mailing list.<br>
> > > > ><br>
> > > > ><br>
> > > > > Some other raspberry specific topics could be the<br>
> following.<br>
> > > Note that<br>
> > > > > this are only suggestions. I don't want to force you<br>
> to do<br>
> > > any of them<br>
> > > > > if you don't like them:<br>
> > > > ><br>
> > > > > - Documentation how you run an application in QEMU /<br>
> on real<br>
> > > hardware<br>
> > > > > for the user manual:<br>
> > > > ><br>
> > > ><br>
> > > <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>
> > > > ><br>
> > > > > - A configuration for RTEMS tester that uses the QEMU or<br>
> > > real hardware<br>
> > > > > (I think the pi3 allows network boot?). This allows<br>
> regular<br>
> > > test runs<br>
> > > > > for this BSP:<br>
> > > > ><br>
> > > <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>
> > > > ><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<br>
> would<br>
> > > be great if<br>
> > > > > you could add a configuration to create raspberry SD<br>
> images<br>
> > > to it:<br>
> > > > ><br>
> > > <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<br>
> already<br>
> > > there and<br>
> > > > > integrate it. If you want to work with libbsd:<br>
> Testing or<br>
> > > porting<br>
> > > > > Ethernet support could be something.<br>
> > > > ><br>
> > > > > - You most likely want to do something with RPi in<br>
> your GSoC<br>
> > > too. So<br>
> > > > > maybe some comments ("x is already done", "y seems to be<br>
> > > still open")<br>
> > > > > for the ticket for it would be nice too:<br>
> > > > <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<br>
> where<br>
> > > 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<br>
> > > someone who<br>
> > > > 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>>><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>><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>>>><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>><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>>><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>><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>>>>><br>
> > > > >>> <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><br>
> <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>><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>>>><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>><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>>><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>><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<br>
> documentation<br>
> > > update<br>
> > > > >> for the<br>
> > > > >>> > quick-start section<br>
> > > > >>> > a few months ago. But no one took a look at<br>
> it. Can you<br>
> > > > have a<br>
> > > > >>> look at it?<br>
> > > > >>><br>
> > > > >>> I'll try to have a look at it soon.<br>
> > > > >>><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<br>
> please just<br>
> > > send a<br>
> > > > >> reminder<br>
> > > > >>> one or two weeks later. It's quite likely<br>
> that the<br>
> > > patch just<br>
> > > > >> slipped<br>
> > > > >>> the attention.<br>
> > > > >>><br>
> > > > >>> Normally I leave documentation patches to our<br>
> native<br>
> > > 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<br>
> can add<br>
> > > 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> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>>><br>
> > > <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<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<br>
> > > protocols<br>
> > > > subject to interception and tampering.<br>
> > > ><br>
> > ><br>
> > _______________________________________________<br>
> > devel mailing list<br>
> > <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<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>
</blockquote></div></div>