GSoC 2014 | Poring RTEMS for OpenRISC

[Joel Sherrill]

On Mar 3, 2014 8:23 AM, Gedare Bloom <gedare at rtems.org> wrote:
>
> Hesham,
>
> The first question to figure out is why was the older port dropped.

This I can answer. The tool chain rotted and had no maintainer. I also recall not having a simulator to test on.

The final issue was some discrepancy between multiple openrisc CPU projects where I thought the focus on the architecture we had a port to was losing interest from them.

> The second is what is your interest in porting to OpenRISC?

And who would use it?

Long term a port needs to be to a viable architecture from a "is it alive" view  this includes the cpu, tools, a way for us to test, etc

> Gedare
>
> On Sun, Mar 2, 2014 at 12:39 AM, Hesham Moustafa
> <heshamelmatary at gmail.com> wrote:
> > Hi,
> >
> > I am thinking of porting RTEMS for OpenRISC as a proposal for GSoC project
> > this year.
> > I know there was an older port, but it's not available anymore on the
> > current RTEMS mainsteam.
> > Would this project be of useful to RTEMS and suitable for GSoC ?
> >
> > Thanks,
> > Hesham
> >
> > _______________________________________________
> > rtems-devel mailing list
> > rtems-devel at rtems.org
> > http://www.rtems.org/mailman/listinfo/rtems-devel
> >
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20140303/50c05643/attachment-0001.html>