On Wed, Nov 19, 2014 at 8:58 PM, Stefan Wallentowitz <[email protected]> wrote: > Dear all, > > I am about to finish my work on clearing up the newlib port. I already > discussed some stuff with upstream and will try to get it there asap. These > are the major changes: > * License change from GPL to BSD. I asked all contributors and essentially > only had to rewrite the uart stuff, write() and some minor stuff. I will > double-check again I did not forget anybody, which is slightly complicated > due to moving around this code and me splitting it up > * All or1k-support moved to libglosss, this is how it should be I think > * or1k-elf is a sys now to solve the issue with dynamic reentrancy vs. the > current upstream (for rtems) > * spr-defs.h is or1k-sprs.h now which is generated from > openrisc/or1k-headers under BSD. This will break your current code due to > new macro names, I will write a small python script to help your converting > macro names the next weeks and put it on the site above > * Multicore is already builtin. Currently it is built extra as libor1k_mc.a > and crt0_mc.o (see wallento/or1k-gcc:multicore for picking it up). This may > change to a multilib in the near future. > * Code re-organization (clear namespaces, more documentation, splitup asm, > combine syscalls, boards into subdir, ...) > > This is the website for the port: http://wallento.github.io/or1k-newlib/ > I added some pre-built archives for download (that need to go to > /opt/or1k-toolchain, still need to describe how to relocate). Furthermore > there are continuous builds from the git repositories whenever either > openrisc/or1k-src, openrisc/or1k-gcc or wallento/or1k-newlib change. The > build status is published at http://lis.ei.tum.de/jenkins/ and the archives > can be downloaded at the aforementioned website. > Finally, here is the documentation of or1k-support: > http://wallento.github.io/or1k-newlib/docs/html/modules.html > > Please be so kind and help me with testing, code review and license checking > if you find the time. Any help is welcome. The code is roughly tested and I > will continue with automated regression tests the next days, before packing > a patch proposal for upstream. > > Thanks for your time. > > Best regards, > Stefan > _______________________________________________ > OpenRISC mailing list > [email protected] > http://lists.openrisc.net/listinfo/openrisc
Hi Stefan, Excellent work! Thanks for all the hard work, and I'll make sure to report any problems that I might come across //Olof _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
