On Wed, Nov 18, 2020 at 11:57 AM John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx> wrote: > On 11/18/20 11:48 AM, Arnd Bergmann wrote: > >>> 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. > > Ah, right. dpkg still has support for or1k [1], so generally it should be possible > then to use the tool rebootstrap [2] to cross-build a Debian base system for OpenRISC > from source. > > We could add it to Debian Ports if there is sufficient interest and usable hardware > available. I think hardware is mainly available in form of FPGAs, which means the hardware capabilities are fairly limited. I only mentioned it because it was a recent (from i.e. this century) big-endian target that already had the beginnings of a Debian port. Otherwise it's probably similar to arc, microblaze, nios2, xtensa, csky or nds32: if someone really wanted a Debian port and is willing to do the work, it could be done, but in practice any of those would be better off a minimum custom user space (buildroot, yocto, ...) anyway. In practice, new 32-bit ports may be limited to machines that can build packages on 64-bit hardware with enough memory, as it is currently done on i386, mipsel, armel, armhf, and the ports for hppa, powerpc, and x32. This means arc, microblaze and rv32 could still be supported once there is sufficient kernel support for their 64-bit targets. Arnd
