Procedure to submit new port (CR16 processor)

[Pompapathi V Gadad]

Hello Ian,
Thanks for the valuable information.

>> My GCC assignment/disclaimer process with the FSF is complete. It
>> would be greatly appreciated, if someone can provide information about
>> the following:
>> a) Can the write permissions to port specific files can be obtained
>> even before submitting the files? How to get GCC SVN write permissions?
>>     
>
> The first step is to send the proposed patch to gcc-patches.  Get the
> patch approved, which will normally involve some give-and-take with
> the maintainers.  Then apply for write permission to the SVN
> repository, and commit the patch.
>   
OK. Let me submit the patch for CR16 first and go through the approval 
process.


>> b) I would also like to maintain the CRX (National Semiconductor's
>> 32-bit processor) port. What is the procedure to request transfer in
>> maintainership of CRX port? If there is no such thing called "transfer
>> of maintainership", then would it be possible to co-maintain the CRX
>> port?
>>     
> The first step would be to talk to the current maintainer of the CRX
> port, Paul Woegerer, and make sure that he agrees.
>
> Usually the steering committee would like to see some track record of
> successful patch submission before granting maintainer status.  For
> example, it needs to be clear that you understand the basic
> formatting, patch submission, and patch approval rules.  So you should
> probably go through the exercise of submitting the CR16 port before
> becoming maintainer of the CRX port.
>   
The email id of Paul Woegerer is not valid as he is not with National 
anymore. Therefore, there is no way to contact Paul on this matter.
Our team in National has started handling tool chains related to CRX and 
CR16 cores. May be, I should go ahead with submitting the CR16 port first.


Thanks a lot,
-Pompa
-------------------------------------
Pompapathi V Gadad
CR Tool Chain Team
National Semiconductor Corporation