RE: eCos port to IDT processors

RE: eCos port to IDT processors

[Chang, Sandra]

Jonathan:
IDT will submit the code - what email do we send the code to?
thanks
Sandra

Sandra Chang
Strategic Partner Program Manager
Internetworking Products Division
tel:  408-988-5647
fax: 408-330-1748
sandra.chang@idt.com


-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
Sent: Thursday, February 13, 2003 10:52 AM
To: Chang, Sandra
Cc: 'ecos-maintainers@sources.redhat.com'; Tim Michals
Subject: Re: eCos port to IDT processors


Chang, Sandra wrote:
> Jonathan:
> Do you need to process the assignment before we can ship the code?

No, you can ship the code now, although it may differ from what eventually 
gets incorporated into the master repository in minor ways.

As it happens, I had just sent a mail to Tim asking if he had it. Whoever 
wants to send it I don't mind :-).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

Re: eCos port to IDT processors

[Jonathan Larmour]

Chang, Sandra wrote:
> Jonathan:
> IDT will submit the code - what email do we send the code to?

ecos-patches@sources.redhat.com

Only send the new files and the patches to the changed files - don't send 
a whole repository though - that's quite big :-).

Thanks!

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

Re: eCos port to IDT processors

[Jonathan Larmour]

Chang, Sandra wrote:
> Jonathan:
> Do you need to process the assignment before we can ship the code?

No, you can ship the code now, although it may differ from what eventually 
gets incorporated into the master repository in minor ways.

As it happens, I had just sent a mail to Tim asking if he had it. Whoever 
wants to send it I don't mind :-).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

RE: eCos port to IDT processors

[Chang, Sandra]

Jonathan:
Do you need to process the assignment before we can ship the code?
thanks
Sandra

Sandra Chang
Strategic Partner Program Manager
Internetworking Products Division
tel:  408-988-5647
fax: 408-330-1748
sandra.chang@idt.com


-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
Sent: Thursday, February 13, 2003 10:07 AM
To: Chang, Sandra
Cc: 'ecos-maintainers@sources.redhat.com'
Subject: Re: eCos port to IDT processors


Chang, Sandra wrote:
> Jonathan:
> We sent it beginning of December, 12/3/02, I believe, to the Red Hat
address
> in Raleigh, attn the Legal Department.
> 
> The assignment was filled out by Tim Michals, our contractor, and IDT
signed
> the waiver.
> 
> We wanted to submit both our RC32334 based and RC32438 based codes.

Ahh. My mistake. Yes we do have that. Thankyou for prodding me :-). I'll 
do it later today when waiting for builds.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

Re: eCos port to IDT processors

[Jonathan Larmour]

Chang, Sandra wrote:
> Jonathan:
> We sent it beginning of December, 12/3/02, I believe, to the Red Hat address
> in Raleigh, attn the Legal Department.
> 
> The assignment was filled out by Tim Michals, our contractor, and IDT signed
> the waiver.
> 
> We wanted to submit both our RC32334 based and RC32438 based codes.

Ahh. My mistake. Yes we do have that. Thankyou for prodding me :-). I'll 
do it later today when waiting for builds.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

RE: eCos port to IDT processors

[Chang, Sandra]

Jonathan:
We sent it beginning of December, 12/3/02, I believe, to the Red Hat address
in Raleigh, attn the Legal Department.

The assignment was filled out by Tim Michals, our contractor, and IDT signed
the waiver.

We wanted to submit both our RC32334 based and RC32438 based codes.

thanks
Sandra

Sandra Chang
Strategic Partner Program Manager
Internetworking Products Division
tel:  408-988-5647
fax: 408-330-1748
sandra.chang@idt.com


-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
Sent: Wednesday, February 12, 2003 5:44 PM
To: Chang, Sandra
Cc: 'ecos-maintainers@sources.redhat.com'
Subject: Re: eCos port to IDT processors


Chang, Sandra wrote:
> Jonathan:
> We've been trying to submit the eCos code for some IDT processors, and was
> told that we needed to submit the copyright assignment - we've done that
> already, so I'm trying to find out 1) how do we verify that it's been
> received 2) what we need to refer to when submitting the code to
> ecos-patches email that is refered to below.

Hmm. We haven't been notified of the assignment arriving at Red Hat (but 
we aren't Red Hat :-)). When did you send it? Once I know I'll chase up 
Red Hat.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

Re: eCos port to IDT processors

[Jonathan Larmour]

Chang, Sandra wrote:
> Jonathan:
> We've been trying to submit the eCos code for some IDT processors, and was
> told that we needed to submit the copyright assignment - we've done that
> already, so I'm trying to find out 1) how do we verify that it's been
> received 2) what we need to refer to when submitting the code to
> ecos-patches email that is refered to below.

Hmm. We haven't been notified of the assignment arriving at Red Hat (but 
we aren't Red Hat :-)). When did you send it? Once I know I'll chase up 
Red Hat.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

RE: eCos port to IDT processors

[Chang, Sandra]

Jonathan:
We've been trying to submit the eCos code for some IDT processors, and was
told that we needed to submit the copyright assignment - we've done that
already, so I'm trying to find out 1) how do we verify that it's been
received 2) what we need to refer to when submitting the code to
ecos-patches email that is refered to below.

thanks for your help,
Regards,
Sandra

Sandra Chang
Strategic Partner Program Manager
Internetworking Products Division
tel:  408-988-5647
fax: 408-330-1748
sandra.chang@idt.com


-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com]
Sent: Wednesday, October 16, 2002 6:39 AM
To: Ferguson, Ian
Cc: 'ecos-maintainers@sources.redhat.com'; Chang, Sandra
Subject: Re: eCos port to IDT processors


Ferguson, Ian wrote:
> IDT has just completed (via an external contractor very familiar with the
> eCos operating system) a eCos port (v2.0) to an existing embedded
processor.
> This CPU core uses a 32-bit MIPS CPU core.
> 
> I have looked quickly through the FAQ and the license agreement, but I
> wanted to check with you on the next steps we must take to get this code
> released via yourselves into the public domain.
> 
> Should we be emailing source code over to someone there once we sign the
> license agreement?

Well, the first thing to be aware of with respect to the licence is that 
most of the web site refers to the licence for eCos 1.3.1, which, while it 
is the "latest" release, is in fact a very old release. The licence for 
new code has in fact changed. So be sure you are using the new licence 
text based on the GPL and not the RHEPL.

The next step in any case is to get the copyright assignment sorted. That 
should still be mailed to Red Hat. See 
http://sources.redhat.com/ecos/assign.html for the two forms required for 
that. The developer(s) sign the form and IDT sign the copyright disclaimer 
form.

Then, finally :-), you send the code to ecos-patches@sources.redhat.com 
where a maintainer will go through it and apply it. It's good to split it 
up into manageable chunks if possible rather than a massive patch. Each 
patch needs review, and the maintainer may give you review comments 
indicating if something could be done a better way. Although most times 
the maintainer will just make the changes themselves anyway!

After that, it's checked in and freely available with the main eCos 
sources to the world!

> Sorry for such a basic question, but as it is the first time for us in the
> eCos world, we have a bit of a learning curve to go up.

No problems. We'll help where we can :-).

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

Re: eCos port to IDT processors

[Jonathan Larmour]

Ferguson, Ian wrote:
> IDT has just completed (via an external contractor very familiar with the
> eCos operating system) a eCos port (v2.0) to an existing embedded processor.
> This CPU core uses a 32-bit MIPS CPU core.
> 
> I have looked quickly through the FAQ and the license agreement, but I
> wanted to check with you on the next steps we must take to get this code
> released via yourselves into the public domain.
> 
> Should we be emailing source code over to someone there once we sign the
> license agreement?

Well, the first thing to be aware of with respect to the licence is that 
most of the web site refers to the licence for eCos 1.3.1, which, while it 
is the "latest" release, is in fact a very old release. The licence for 
new code has in fact changed. So be sure you are using the new licence 
text based on the GPL and not the RHEPL.

The next step in any case is to get the copyright assignment sorted. That 
should still be mailed to Red Hat. See 
http://sources.redhat.com/ecos/assign.html for the two forms required for 
that. The developer(s) sign the form and IDT sign the copyright disclaimer 
form.

Then, finally :-), you send the code to ecos-patches@sources.redhat.com 
where a maintainer will go through it and apply it. It's good to split it 
up into manageable chunks if possible rather than a massive patch. Each 
patch needs review, and the maintainer may give you review comments 
indicating if something could be done a better way. Although most times 
the maintainer will just make the changes themselves anyway!

After that, it's checked in and freely available with the main eCos 
sources to the world!

> Sorry for such a basic question, but as it is the first time for us in the
> eCos world, we have a bit of a learning curve to go up.

No problems. We'll help where we can :-).

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

eCos port to IDT processors

[Ferguson, Ian]

IDT has just completed (via an external contractor very familiar with the
eCos operating system) a eCos port (v2.0) to an existing embedded processor.
This CPU core uses a 32-bit MIPS CPU core.

I have looked quickly through the FAQ and the license agreement, but I
wanted to check with you on the next steps we must take to get this code
released via yourselves into the public domain.

Should we be emailing source code over to someone there once we sign the
license agreement?

Sorry for such a basic question, but as it is the first time for us in the
eCos world, we have a bit of a learning curve to go up.

Regards
Ian Ferguson
Strategic Marketing Manager
IDT
Ph: 408 492 8363
Email: ian.ferguson@idt.com