On Wed, Nov 18, 2020 at 11:24 AM John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx> wrote: > On 11/18/20 9:40 AM, Geert Uytterhoeven wrote: > > On Wed, Nov 18, 2020 at 9:27 AM Arnd Bergmann <arnd@xxxxxxxxxx> wrote: > >>I'm surprised nobody so far tried restarting the openrisc port, > >> which got dropped when it appeared the corresponding gcc port would not > >> be upstreamed. > > > > I guess that is partly due to the limited availability of OpenRISC > > hardware? I had it running on a DE0-NANO, but 32 MiB RAM and > > no Ethernet doesn't bring you far... > > The Debian wiki has some information on armeb and OpenRISC: > > > https://wiki.debian.org/ArmPorts > > https://wiki.debian.org/OpenRISC > > Apparently, interest for armeb was lost after people realized the hardware > being used could run little-endian as well and OpenRISC apparently had > licensing issues. Right, my point above was that the licensing issues were resolved last year when the gcc port finally landed in gcc-9. Arnd
