Port Contribution

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Port Contribution

Richard Rauch
Hi all,

We have finished now our announced port to Atmel ARM9 microcontroller
AT91SAM9.
Next we want to contribute this port.

We have a lot of questions how to do this:

How we have to prepare the software?
Where we have to upload?
Is there any paper work to do?

We will need some assistance for this process. It is the first time, that we
contributing to the ecos community!
 
Thanks

Richard

 
Richard Rauch
email: [hidden email]
_______________________________________________

ITR GmbH
Informationstechnologie Rauch
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
_______________________________________________


Reply | Threaded
Open this post in threaded view
|

RE: Port Contribution

Christophe Coutand
Hi Richard,

This is what I know about the contribution process:

#1 To submit contributions, you need your copyright assignment from the
FSF in place: http://ecos.sourceware.org/assign.html

#2 Patches should be submitted using Bugzilla
(http://bugs.ecos.sourceware.org/), setting the Component field to
Patches and contributions. Even if it is obsolete, I still put the eCos
patch mailing list in CC of the Bugzilla case.

#3 Check this post for eCos coding style:
http://ecos.sourceware.org/ml/ecos-devel/2011-03/msg00016.html

#4 As commented by Ilija, it is better to submit diff in plain text
format (http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219)

#5 Changes in ecos.db are not sent as diff. Submit an ecos.db than
contains only your added entries.

#6 Note that there is a work in progress to add ARM9 support to eCos:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819

Christophe

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Richard Rauch
Sent: 12. mai 2011 08:25
To: [hidden email]
Subject: Port Contribution

Hi all,

We have finished now our announced port to Atmel ARM9 microcontroller
AT91SAM9.
Next we want to contribute this port.

We have a lot of questions how to do this:

How we have to prepare the software?
Where we have to upload?
Is there any paper work to do?

We will need some assistance for this process. It is the first time,
that we
contributing to the ecos community!
 
Thanks

Richard

 
Richard Rauch
email: [hidden email]
_______________________________________________

ITR GmbH
Informationstechnologie Rauch
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
_______________________________________________


Reply | Threaded
Open this post in threaded view
|

AW: Port Contribution

Richard Rauch
Thanks for the fast reply.

I know this review process. Our port is based on this port, too.
So maybe it would be better to await the results of this review, before
contributing our own port?
But unfortunately there is less progress on this task.  


Hi Richard,

This is what I know about the contribution process:

#1 To submit contributions, you need your copyright assignment from the FSF
in place: http://ecos.sourceware.org/assign.html

#2 Patches should be submitted using Bugzilla
(http://bugs.ecos.sourceware.org/), setting the Component field to Patches
and contributions. Even if it is obsolete, I still put the eCos patch
mailing list in CC of the Bugzilla case.

#3 Check this post for eCos coding style:
http://ecos.sourceware.org/ml/ecos-devel/2011-03/msg00016.html

#4 As commented by Ilija, it is better to submit diff in plain text format
(http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219)

#5 Changes in ecos.db are not sent as diff. Submit an ecos.db than contains
only your added entries.

#6 Note that there is a work in progress to add ARM9 support to eCos:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819

Christophe

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Richard Rauch
Sent: 12. mai 2011 08:25
To: [hidden email]
Subject: Port Contribution

Hi all,

We have finished now our announced port to Atmel ARM9 microcontroller
AT91SAM9.
Next we want to contribute this port.

We have a lot of questions how to do this:

How we have to prepare the software?
Where we have to upload?
Is there any paper work to do?

We will need some assistance for this process. It is the first time, that we
contributing to the ecos community!
 
Thanks

Richard

 
Richard Rauch
email: [hidden email]
_______________________________________________

ITR GmbH
Informationstechnologie Rauch
Schnepfenreuther Hauptstrasse 27b
D-90425 Nuernberg
_______________________________________________


Reply | Threaded
Open this post in threaded view
|

Re: Port Contribution

Ilija Kocho [Илија Кочо]
In reply to this post by Christophe Coutand
On 12.05.2011 10:39, Christophe Coutand wrote:

> Hi Richard,
>
> This is what I know about the contribution process:
>
> #1 To submit contributions, you need your copyright assignment from the
> FSF in place: http://ecos.sourceware.org/assign.html
>
> #2 Patches should be submitted using Bugzilla
> (http://bugs.ecos.sourceware.org/), setting the Component field to
> Patches and contributions. Even if it is obsolete, I still put the eCos
> patch mailing list in CC of the Bugzilla case.
>
> #3 Check this post for eCos coding style:
> http://ecos.sourceware.org/ml/ecos-devel/2011-03/msg00016.html
>
> #4 As commented by Ilija, it is better to submit diff in plain text
> format (http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219)
>
> #5 Changes in ecos.db are not sent as diff. Submit an ecos.db than
> contains only your added entries.

This seems like good idea as ecos.db diff for some reason often contains
some unwanted stuff in addition to your entries.

Also I find it useful to group /hal/ and /devs/ (if any) packages in
separate diffs so they could be reviewed and committed independently.

> #6 Note that there is a work in progress to add ARM9 support to eCos:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819
>
> Christophe
>
> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of Richard Rauch
> Sent: 12. mai 2011 08:25
> To: [hidden email]
> Subject: Port Contribution
>
> Hi all,
>
> We have finished now our announced port to Atmel ARM9 microcontroller
> AT91SAM9.
> Next we want to contribute this port.
>
> We have a lot of questions how to do this:
>
> How we have to prepare the software?
> Where we have to upload?
> Is there any paper work to do?
>
> We will need some assistance for this process. It is the first time,
> that we
> contributing to the ecos community!
>  
> Thanks
>
> Richard
>
>  
> Richard Rauch
> email: [hidden email]
> _______________________________________________
>
> ITR GmbH
> Informationstechnologie Rauch
> Schnepfenreuther Hauptstrasse 27b
> D-90425 Nuernberg
> _______________________________________________
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Port Contribution

Sergei Gavrikov-4
On Fri, 13 May 2011, Ilija Kocho wrote:

> On 12.05.2011 10:39, Christophe Coutand wrote:
> > Hi Richard,
> >
> > This is what I know about the contribution process:
> >
> > #1 To submit contributions, you need your copyright assignment from the
> > FSF in place: http://ecos.sourceware.org/assign.html
> >
> > #2 Patches should be submitted using Bugzilla
> > (http://bugs.ecos.sourceware.org/), setting the Component field to
> > Patches and contributions. Even if it is obsolete, I still put the eCos
> > patch mailing list in CC of the Bugzilla case.
> >
> > #3 Check this post for eCos coding style:
> > http://ecos.sourceware.org/ml/ecos-devel/2011-03/msg00016.html

We are in no case do not insist on using ``indent'' !

Instead, I would refer to this original source
http://ecos.sourceware.org/docs-latest/ref/hal-porting-coding-conventions.html

Also I have would quoted (added)

    >>> Do not leave trailing whitespace at the ends of lines.  Some
    >>> editors with "smart" indentation will insert whitespace at the
    >>> beginning of new lines as appropriate, so you can start typing the
    >>> next line of code right away.  However, some such editors do not
    >>> remove the whitespace if you end up not putting a line of code
    >>> there, such as if you leave a blank line.  As a result, you end up
    >>> with lines containing trailing whitespace.


NOTE: But, the eCos copyright headers in the sources are an exception.

> > #4 As commented by Ilija, it is better to submit diff in plain text
> > format (http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001219)
> >
> > #5 Changes in ecos.db are not sent as diff. Submit an ecos.db than
> > contains only your added entries.
>
> This seems like good idea as ecos.db diff for some reason often contains
> some unwanted stuff in addition to your entries.
>
> Also I find it useful to group /hal/ and /devs/ (if any) packages in
> separate diffs so they could be reviewed and committed independently.
>
> > #6 Note that there is a work in progress to add ARM9 support to eCos:
> > http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819
> >
> > Christophe
> >
> > -----Original Message-----
> > From: [hidden email]
> > [mailto:[hidden email]] On Behalf Of Richard Rauch
> > Sent: 12. mai 2011 08:25
> > To: [hidden email]
> > Subject: Port Contribution
> >
> > Hi all,
> >
> > We have finished now our announced port to Atmel ARM9 microcontroller
> > AT91SAM9.
> > Next we want to contribute this port.
> >
> > We have a lot of questions how to do this:
> >
> > How we have to prepare the software?
> > Where we have to upload?
> > Is there any paper work to do?
> >
> > We will need some assistance for this process. It is the first time,
> > that we
> > contributing to the ecos community!
> >  
> > Thanks
> >
> > Richard
> >
> >  
> > Richard Rauch
> > email: [hidden email]
> > _______________________________________________
> >
> > ITR GmbH
> > Informationstechnologie Rauch
> > Schnepfenreuther Hauptstrasse 27b
> > D-90425 Nuernberg
> > _______________________________________________
> >
> >
>