public inbox for
 help / color / mirror / Atom feed
From: "Austin, Brian" <>
To: "H Hartley Sweeten" <>
Cc: "Jonathan Larmour" <>,
	"Gary Thomas" <>,
	        "eCos Maintainers" <>
Subject: RE: Cirrus Logic EP93XX ARM9 support
Date: Wed, 18 Nov 2009 16:33:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hey guys,

I have been trying to find the paper work to mail off to the FSF, but
cant find it.  Legal gave it the go ahead.

I totally folded on this and am sorry,

Can you point me to the person at the FSF to resend me the paper work,
so I can sign it and send it off.

Sorry again for the fowlup.

Brian Austin

-----Original Message-----
From: H Hartley Sweeten [] 
Sent: Wednesday, November 18, 2009 10:30 AM
To: Austin, Brian
Cc: Jonathan Larmour; Gary Thomas;;
eCos Maintainers
Subject: RE: Cirrus Logic EP93XX ARM9 support

On Thursday, September 17, 2009 2:19 PM, Austin, Brian wrote:
> Crap!  Sorry guys,
> I'll mail that off.

Hello Brian,

Hate to be a pain but, did you ever get the paperwork submitted to the
FSF to transfer the copyright assignment for the Cirrus ep93xx eCos


-----Original Message-----
From: H Hartley Sweeten [] 
Sent: Thursday, September 17, 2009 4:11 PM
To: Austin, Brian
Cc: Jonathan Larmour; Gary Thomas;;
eCos Maintainers
Subject: RE: Cirrus Logic EP93XX ARM9 support

On Thursday, September 17, 2009 1:54 PM, Jonathan Larmour wrote:
> H Hartley Sweeten wrote:
>> On Sunday, June 14, 2009 6:19 PM, Gary Thomas wrote:
>>> Jonathan Larmour wrote:
>>>> Gary Thomas wrote:
>>>>> H Hartley Sweeten wrote:
>>>>>> Hello all,
>>>>>> Does anyone know the status of the Cirrus Logic EP93XX ARM9
>>>>>> Was the copyright assignment to the FSF completed?  If so, would
>>>>>> be possible to at least get the new file pieces of the patch into
>>>>>> CVS so that they can be cleaned up?  The diff appears fairly
>>>>>> except for a couple of issues.  Following are the files in the
>>>>> AFAIK, we've not had official confirmation from FSF yet.
>>>> Unless they've submitted it very recently, then I suspect they
>>>> made an assignment.
>>> They claim to have submitted it [not so] recently - probably April
>>> timeframe, maybe a bit later.  It should be in the logs (I don't
>>> time to search right now).
>> Does anyone know the status of this?
>> I have a number of updates/cleanups I would like to submit but the
>> original patch is still not in CVS.
> I'm afraid there is still no record with the FSF that they've
submitted an 
> assignment. Either the FSF haven't updated their master database, or
> never actually completed the assignment. I think you'd need to ask

Hello Brian,

On May 12, 2009 you posted this message to the ecos-discuss list:

> I am sending off the contracts to the FSF, and have posted the patch
> the Cirrus Port's to the ecos bugzilla.  Hopefully someone will start
> forward port the code base.

Did the contracts ever get submitted?  Your patch is still in the ecos
bugzilla but cannot be added until they receive the official
from FSF.


  reply	other threads:[~2009-11-18 16:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2009-06-10 19:42 ` Gary Thomas
2009-06-14 21:02   ` Jonathan Larmour
2009-06-15  1:19     ` Gary Thomas
2009-09-16 21:31       ` H Hartley Sweeten
2009-09-17  8:54         ` John Dallaway
2009-09-17 20:54         ` Jonathan Larmour
2009-09-17 21:10           ` H Hartley Sweeten
2009-09-17 21:18             ` Austin, Brian
2009-11-18 16:31               ` H Hartley Sweeten
2009-11-18 16:33                 ` Austin, Brian [this message]
2009-11-19  9:37                   ` John Dallaway
2009-11-19 18:38                   ` Jonathan Larmour
2010-03-13  0:08                     ` H Hartley Sweeten
2009-08-07 15:36   ` John Dallaway
2009-08-07 15:53     ` Austin, Brian
2009-08-07 16:19       ` John Dallaway

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).