Future of or1k RTEMS support?

[Hesham Almatary]

Hi Sebastian,

Yes, I agree with you. Furthermore, most of the or1k hardware and software
folks are moving to riscv now.

Should we make it obsolete?

Cheers,
Hesham

On Thu, 26 Jul 2018 at 7:10 am, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello,
>
> the or1k ecosystem has a major problem with their non-FSF GCC from my
> point of view which is maintained here:
>
> https://github.com/openrisc/or1k-gcc
>
> The last commit was in 2016.  It looks like a dead project to me.
>
> Given the momentum RISC-V has currently why would someone still want to
> use or1k? All RISC-V tools are upstream and well maintained. It is the
> target with the most helpful and responsive maintainers that I worked
> with so far.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> <https://maps.google.com/?q=Dornierstr.+4,+D-82178+Puchheim,+Germany&entry=gmail&source=g>
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

-- 
Hesham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180726/fa460f69/attachment-0002.html>