<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 11/13/2014 2:46 PM, Hesham Moustafa
wrote:<br>
</div>
<blockquote
cite="mid:CA+wsVCA5ruZSbCd=U-FCuowP3gM7+KAPDxEGG2iKqMKAtfwVmw@mail.gmail.com"
type="cite">Hi,<br>
<br>
<div>Thanks a lot for the patches. I will let you know with the
status. </div>
<div>One thing I want someone to confirm about is that I will not
be </div>
<div>able to use/copy any of the GPL licensed code there [1],
right?</div>
<div><br>
</div>
</blockquote>
Not as part of anything that you submit for inclusion in RTEMS. <br>
I don't know how this particular setup works. I can see host <br>
utilities that you would just get from there and I don't know that<br>
we care about those licenses. <br>
<br>
And there might be libraries you want to use with your experiments<br>
that is GPL but not submit to RTEMS. That is OK if you manage how<br>
it comes in contact with your own application code. <br>
<br>
Please avoid it wherever possible. If there is some run-time library<br>
we need to ask for relicensing, then we can go that round. <br>
<blockquote
cite="mid:CA+wsVCA5ruZSbCd=U-FCuowP3gM7+KAPDxEGG2iKqMKAtfwVmw@mail.gmail.com"
type="cite">
<div>[1] <a moz-do-not-send="true"
href="https://github.com/adapteva/epiphany-libs">https://github.com/adapteva/epiphany-libs</a></div>
<div><br>
</div>
<div>Regards,</div>
<div>Hesham</div>
<br>
<div class="gmail_quote">On Thu Nov 13 2014 at 6:47:28 PM Joel
Sherrill <<a moz-do-not-send="true"
href="mailto:joel.sherrill@oarcorp.com">joel.sherrill@oarcorp.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi<br>
<br>
I couldn't get gdb og gcc to build even for epiphany-elf but
I did<br>
include patch that I think is all that is needed for RTEMS.<br>
<br>
I did manage to build binutils from their repo for both elf<br>
and rtems variants. <br>
<br>
At least it is a starting point. You can work with their<br>
community to get their tools built as epiphany-elf and<br>
then just change the target.</div>
<div bgcolor="#FFFFFF" text="#000000"><br>
<br>
--joel</div>
<div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<div>On 11/13/2014 12:22 PM, Hesham Moustafa wrote:<br>
</div>
<blockquote type="cite"><br>
<br>
<div class="gmail_quote">On Thu Nov 13 2014 at 5:58:25 PM
Joel Sherrill <<a moz-do-not-send="true"
href="mailto:joel.sherrill@oarcorp.com"
target="_blank">joel.sherrill@oarcorp.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On November 13, 2014 11:56:32 AM CST, Hesham Moustafa
<<a moz-do-not-send="true"
href="mailto:heshamelmatary@gmail.com"
target="_blank">heshamelmatary@gmail.com</a>>
wrote:<br>
>Hi,<br>
><br>
><br>
>I want to let you know that I found their main
repos [1] Can I start<br>
>from there? Imitating what has been done with
OpenRISC?<br>
><br>
<br>
Basically. Except you only need their repos for
binutils and gdb. We use GCC and Newlib from upstream.<br>
<br>
</blockquote>
<div>Great, I am waiting for these patches. </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> I
have binutils patches<br>
<br>
>[1] <a moz-do-not-send="true"
href="https://github.com/adapteva" target="_blank">https://github.com/adapteva</a><br>
><br>
><br>
>Regards,<br>
><br>
>Hesham<br>
><br>
>On Thu Nov 13 2014 at 3:29:14 PM Hesham Moustafa<br>
><<a moz-do-not-send="true"
href="mailto:heshamelmatary@gmail.com"
target="_blank">heshamelmatary@gmail.com</a>>
wrote:<br>
><br>
>On Thu Nov 13 2014 at 2:59:33 PM Joel Sherrill<br>
><<a moz-do-not-send="true"
href="mailto:joel.sherrill@oarcorp.com"
target="_blank">joel.sherrill@oarcorp.com</a>>
wrote:<br>
><br>
><br>
>On 11/13/2014 8:07 AM, Joel Sherrill wrote:<br>
>><br>
>> On November 13, 2014 6:30:48 AM CST, Hesham
Moustafa<br>
><<a moz-do-not-send="true"
href="mailto:heshamelmatary@gmail.com"
target="_blank">heshamelmatary@gmail.com</a>>
wrote:<br>
>>> Hi all,<br>
>>><br>
>>><br>
>>> I want to ask about the status of RTEMS
toolchain for Epiphany<br>
>>> architecture. I think Joel mentioned that
there are some previous<br>
>>> support for it; and if yes, does the
toolchain need some additional<br>
>>> work?<br>
>> To give you a quick answer, I emailed the
people who did the port.<br>
>There apparently is a github repo with some of it
and some is merged. I<br>
>will dig through the emails and post the proper
links.<br>
>><br>
>> One issue they mentioned was that the gdb
port had many core/thread<br>
>support that made it more than a simple port.<br>
>From Jeremy Bennett:<br>
><br>
>> piphany tool chain development runs on quite
a tight budget, and its<br>
>> GDB implementation is quite complex (it has
to pretend cores are<br>
>> threads, when they don't completely share an
address space). So we<br>
>> haven't had the effort to devote to
upstreaming. And we were<br>
>> reluctant to push the simulator upstream
without a GDB implementation<br>
>> to go with it. You can of course access the
code here:<br>
>><br>
>> <a moz-do-not-send="true"
href="https://github.com/adapteva/epiphany-binutils-gdb"
target="_blank">https://github.com/adapteva/epiphany-binutils-gdb</a><br>
>><br>
>> Epiphany GDB is still in quite substantial
flux, due to the need to<br>
>> support the Eclipse multicore visualizer with
asynchronous and<br>
>> non-stop support.<br>
>The upstream gcc and newlib are OK. But since
binutils and gdb are<br>
>now in a single repo, it will need to come from
the github site until<br>
>it is merged upstream. And obviously patches just
need to go upstream<br>
>to whereever the code is. :)<br>
><br>
>Jeremy also encouraged you to openly discuss
things on their forums.<br>
>He thought you would get good insight and advice
there. And I don't<br>
>doubt that.<br>
><br>
>Thank you, I will.<br>
><br>
>If it is a relatively low volume place, I may
track it. But my email<br>
>volume<br>
>is already high and I don't have time to poke
around on a bulletin<br>
>board.<br>
><br>
>> It will not have RTEMS as a target but that
shouldn't be hard to<br>
>address once we know where the master binutils,
GCC, Newlib, and gdb<br>
>are.<br>
>So do you want me to try to build a toolchain and
get you some starting<br>
>patches?<br>
><br>
>Sure that will definitely help as a starting
point. And if you are so<br>
>busy, you can just drop me HOWTO instructions.<br>
><br>
>> Then you are porting.<br>
>><br>
>>> Regards,<br>
>>><br>
>>> Hesham<br>
>>
_______________________________________________<br>
>> devel mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
>> <a moz-do-not-send="true"
href="http://lists.rtems.org/mailman/listinfo/devel"
target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
><br>
>--<br>
>Joel Sherrill, Ph.D. Director of
Research & Development<br>
><a moz-do-not-send="true"
href="mailto:joel.sherrill@OARcorp.com"
target="_blank">joel.sherrill@OARcorp.com</a>
On-Line Applications Research<br>
>Ask me about RTEMS: a free RTOS Huntsville AL
35805<br>
>Support Available (256) 722-9985<br>
<br>
</blockquote>
</div>
</blockquote>
<br>
<pre cols="72">--
Joel Sherrill, Ph.D. Director of Research & Development
<a moz-do-not-send="true" href="mailto:joel.sherrill@OARcorp.com" target="_blank">joel.sherrill@OARcorp.com</a> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985</pre>
</div>
</blockquote>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Joel Sherrill, Ph.D. Director of Research & Development
<a class="moz-txt-link-abbreviated" href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985</pre>
</body>
</html>