You need to register in mailman in order to send email via the mailing list. Since this was not done by you earlier, it has now been done manually.
/Marcus >---------- Vidarebefordrat meddelande ---------- >From: Fredrik Bruhn <[email protected]> >To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, openrisc >mailing list <[email protected]> >Cc: >Date: Sat, 7 Apr 2012 23:45:37 +0000 >Subject: RE: [OpenRISC] Subtly forcing the move to OpenCores.org >/* >It is perhaps worth noting that many of the major contributors to this >meeting are not just hobbyists, but are or have been paid professional >contributors. My company, Embecosm, was paid to develop the GCC 4.5 tool >chain to production standard, Olof works for ORSoC AB, Julius used to >work for ORSoC AB, Jonas was paid to develop Linux for OpenRISC. >*/ > >Jeremy, You may want to add that AAC Microtec has been the company behind >most of the funding taking GCC and linux forward on the openrisc architecture lately. >yes, Jonas has been partially funded externally but he, as well as yourself and others >should be honored for putting in way more time that what you have been paid for. > >And we have been very clear based that all work should be dedicated openly and >without commercial interest from any one single business or entity. >Some may remember heated discussions on this throughout the past year. >Hence our patches are publicized at openrisc.net git repository for everyone's benefit. >We've patched newlib and Linux quite significantly lately together with Jonas. Not to forget >all work on U-boot together with Stefan Kristiansson. >The one on opencores has major flaws in the interrupt handler for one. Another is the static directory >problem. >Try moving from /opt/..... to ~/toolchain as an example and the -mboard=..... will stop working. > >We have also been very clear that various previous events has taken us to the decision to not use >OrSoc AB or any of its supplier for any future work relating to openrisc or any forks thereof. >It is also interesting to see the remarks to NASA and space use since our company is leading this >effort. FYI, the first NASA openrisc architecture based Linux computer launch will occur in June this >year to the International Space Station with hardware provided, built, and tested by AAC Microtec and >AAC Microtec North America. > >Maybe this is a good time to fork out LibreRISC to solve Ruben's targeted comments and a long list of >other things at the same time. I fully support Rubens comments that the work should be truly open >and supported by many, but not controlled by a single. > >My last email got trapped by opencores.org and I received an email from Marcus Erlandsson that if I >would try again, it should work. > >I would also like to say that Julius Baxter and Stefan Kristiansson has been outstanding in maturing the >hardware as well as Jeremy getting C++ support amongst other things in place. >A few other announcements that can be made at this is time are the following, >A set of different open/libre/risc ASIC's will likely come off the 90 nm ASIC production line early 2013 and >AAC is committed to provide funding to add position independent code and dynamic linking to the >toolchain during 2012. If anyone is already now close to finishing this we would be happy to offer >a development monetary award for this. > >-Fredrik > >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy Bennett >Sent: Saturday, April 07, 2012 14:27 >To: [email protected]; openrisc mailing list >Subject: Re: [OpenRISC] Subtly forcing the move to OpenCores.org >
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
