This is the mail archive of the
mailing list for the binutils project.
Re: Questions about upstreaming a new port [MRISC32]
- From: Joel Sherrill <joel at rtems dot org>
- To: m <m at bitsnbites dot eu>
- Cc: binutils at sourceware dot org
- Date: Sat, 15 Dec 2018 17:47:33 -0600
- Subject: Re: Questions about upstreaming a new port [MRISC32]
- References: <email@example.com>
- Reply-to: joel at rtems dot org
On Sat, Dec 15, 2018, 4:57 PM m <firstname.lastname@example.org wrote:
> Hello all!
> As part of my hobby CPU project (called MRISC32) I have made an initial
> port of binutils for the CPU.
> Currently I'm fine with keeping the port as a patch series in a personal
> Git repository (that I keep rebasing on top of the latest version of
> binutils). However...
> What are the requirements for getting a port upstreamed? (I can
> understand that a CPU architecture may be out of scope for mainline
> binutils if it's not a "popular CPU", but I'm still interested in
> knowing what you think)
One fundamental requirement is to have a copyright assignment on file with
> More information about the CPU project can be found on GitHub , and
> the binutils port is also maintained in a Git repository on GitHub .
> Best regards,
> Marcus Geelnard
>  https://github.com/mbitsnbites/mrisc32
>  https://github.com/mbitsnbites/binutils-mrisc32