Fw: maintainer change for OpenRisc
Andreas Jaeger
aj@suse.de
Mon Dec 17 07:07:00 GMT 2001
More information about the Binutils mailing list
Mon Dec 17 07:07:00 GMT 2001
- Previous message (by thread): Fw: maintainer change for OpenRisc
- Next message (by thread): GNU ld for Mingw-host
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Marko Mlinar" <markom@opencores.org> writes: > Hi guys! > > Can anybody please help us with this? Or at least can you tell me what is > the > procedure how to add a new port. Is there any FAQ on this? > Do I need CVS write access or must I supply a patch? I guess - but I'm not the official binutils, just a port maintainer: This list is the right place. For adding a new port, we first need a copyright assignment to the FSF. Without assignment to the FSF, we cannot accept the port. Follow the instructions given in http://gcc.gnu.org/ml/gcc/2001-10/msg00593.html. For adding the code, you need to supply a patch. CVS write access helps but is optional. > thanks, > Marko > > ----- Original Message ----- > From: "Marko Mlinar" <markom@opencores.org> > To: <binutils@sources.redhat.com> > Cc: "Johan Rydberg" <jrydberg@opencores.org>; <lampret@opencores.org> > Sent: Thursday, December 13, 2001 9:38 AM > Subject: maintainer change for OpenRisc > > >> Hello! >> >> I am a developer from www.opencores.org , a group of enthusiasts working >> on open hardware projects. One of them is a CPU, named OpenRisc 1000, >> which is ready and we already have complete GNU toolchain (binutils, gcc, >> gdb) >> ready and working. About a year ago there was new architecture added to >> binutils, >> named openrisc. The maintainer was Johan Rydberg, but unfortunately he > was >> unable to finish his work. He would like to pass maintainership to me, so >> that I can Can Johan send an email confirming this? >> put all the tools we already have into official versions. Original work by >> Johan >> was done using CGEN, but ours does not use it. >> If it is possible, we would also like to change openrisc name to something >> more familiar - the name we use: "or1k" (actually architecture name) or >> "or32" (implemetation name). IMO or1k or or32 is less familiar - I would prefer openrisc. But that's your choice, I don't see a technical reason for changing this. >> Who should I contact or what should I do to join bintils group? Join this list (binutils@sources.redhat.com). >> Are there any requests for source code? Let's first get the copyright issues fixed, Andreas -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
- Previous message (by thread): Fw: maintainer change for OpenRisc
- Next message (by thread): GNU ld for Mingw-host
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list