<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 6:54 PM, Gedare Bloom <span dir="ltr"><<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hesham,<br>
<div class=""><br>
On Mon, Mar 3, 2014 at 11:06 AM, Hesham Moustafa<br>
<<a href="mailto:heshamelmatary@gmail.com">heshamelmatary@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Mon, Mar 3, 2014 at 5:06 PM, Joel Sherrill <<a href="mailto:Joel.Sherrill@oarcorp.com">Joel.Sherrill@oarcorp.com</a>><br>
> wrote:<br>
>><br>
>><br>
>> On Mar 3, 2014 8:23 AM, Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br>
>> ><br>
>> > Hesham,<br>
>> ><br>
>> > The first question to figure out is why was the older port dropped.<br>
>><br>
>> This I can answer. The tool chain rotted and had no maintainer. I also<br>
>> recall not having a simulator to test on.<br>
>><br>
>> The final issue was some discrepancy between multiple openrisc CPU<br>
>> projects where I thought the focus on the architecture we had a port to was<br>
>> losing interest from them.<br>
><br>
> Thanks Dr Joel, I also wanted to know the answer :)<br>
> Was this architecture OpenRISC 1000 or another core ?<br>
</div>If the toolchain is up-to-date and there are simulator and real hw<br>
architecture supported, then it can be a feasible project to do a<br>
port.<br>
<div class=""><br></div></blockquote><div>Yes the toolchain is up-to-date and I worked on their or1ksim simulator </div><div>which can be connected to gdb. They support many boards, one of them is</div><div>Atlys FPGA board which I have and worked on and I hope to create a BSP for.</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">
>><br>
>> > The second is what is your interest in porting to OpenRISC?<br>
><br>
> Because I have been working on the last few months on FPGA project ( mips<br>
> microprocessor).<br>
> I wanted to port an OS to an opensource processor, and OpenRISC architecture<br>
> is mature enough to port a complex RTOS like RTEMS.<br>
>><br>
>> And who would use it?<br>
><br>
> People using black box OpenRISC and others interested in Digital design,<br>
> Computer architecture and<br>
> HW/SW interfacing. Something like xilinx zynq ? except that both OpenRISC<br>
> and RTEMS are opensource.<br>
</div>If OpenRISC has settled on a specific reference architecture and has<br>
an adequately active community, then a port would be acceptable.<br>
<div class=""><br></div></blockquote><div>I think they have. OpenRISC 1000 and 1200 architectures are both well supported</div><div>and used, and their community is active.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="">
>><br>
>> Long term a port needs to be to a viable architecture from a "is it alive"<br>
>> view this includes the cpu, tools, a way for us to test, etc<br>
><br>
> Sure, that's what I hope to work on.<br>
</div>In order to have a chance that your proposal will be accepted, you<br>
will need to demonstrate that the openrisc tools work for recent gcc /<br>
newlib with an adequate simulator. Based on wikipedia, you should be<br>
able to cross-compile Linux for the OpenRISC to run on Qemu, or you<br>
may like to just try to get a bare-metal application to run in the<br>
simulator.<br>
<span class=""><font color="#888888"><br></font></span></blockquote><div>I have built their latest toolchain, gcc 4.9.0 and binutils 2.24.51. </div><div>with newlib. A helloworld program is working fine with or1k-elf-run, </div>
<div>or1k-elf-gdb (which connects to their or1ksim simulator) and qemu.</div><div><br></div><div>The questions is, should this project include porting their toolchains to</div><div>RTEMS toolchains (with their copyrights) ? or that may cause some </div>
<div>licence/copyrights problems ? </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><font color="#888888">
Gedare<br>
</font></span><div class=""><div class="h5">>><br>
>> > Gedare<br>
>> ><br>
>> > On Sun, Mar 2, 2014 at 12:39 AM, Hesham Moustafa<br>
>> > <<a href="mailto:heshamelmatary@gmail.com">heshamelmatary@gmail.com</a>> wrote:<br>
>> > > Hi,<br>
>> > ><br>
>> > > I am thinking of porting RTEMS for OpenRISC as a proposal for GSoC<br>
>> > > project<br>
>> > > this year.<br>
>> > > I know there was an older port, but it's not available anymore on the<br>
>> > > current RTEMS mainsteam.<br>
>> > > Would this project be of useful to RTEMS and suitable for GSoC ?<br>
>> > ><br>
>> > > Thanks,<br>
>> > > Hesham<br>
>> > ><br>
>> > > _______________________________________________<br>
>> > > rtems-devel mailing list<br>
>> > > <a href="mailto:rtems-devel@rtems.org">rtems-devel@rtems.org</a><br>
>> > > <a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
>> > ><br>
>> > _______________________________________________<br>
>> > rtems-devel mailing list<br>
>> > <a href="mailto:rtems-devel@rtems.org">rtems-devel@rtems.org</a><br>
>> > <a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>