public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Edgar Grimberg <edgar.grimberg@zylin.com>
Cc: Alex Schuilenburg <alexs@ecoscentric.com>,
	eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] APB - Copyright assignment
Date: Tue, 06 Oct 2009 15:26:00 -0000	[thread overview]
Message-ID: <c09652430910060826u1dbb0c4cj43434107ccae1cfd@mail.gmail.com> (raw)
In-Reply-To: <d0f570ed0910060737u42c2ef71xb2b3bca578dc7ac6@mail.gmail.com>

> Actually, this case is a bit special. Graham Henderson modified files
> that are under eCos (FSF) copyright. I don't know what the legal
> status of the files is now, but they are covered by the GPL (with
> exceptions, as defined by eCos).

The legal status is that FSF *and* Graham has a copyright claim
to the files. The code was originally copyright to FSF and eCos
license. The fact that Graham has a copyright claim to it is unproblematic
for now.

If in the future FSF wants to tinker with the eCos license, then the TSE
becomes a problem, because without Graham's consent(or copyright
assignment), the licensing for his changes can't be changed.

> Of course, the best solution is for me to delete the files that were
> touched by Graham Henderson and rewrite them. This just got high on my
> priority list.

Since the current situation is unproblematic, we can just wait to
see if Graham comes out of the woodwork...

Eventually when nios2ecos is mature enough to be committed to
eCos CVS, then we either ditch the TSE or rewrite it.

(The biggest problem with nios2ecos, IMHO, is that quartus
must be installed to build. This makes it impossible e.g. to put
build tool binaries under version control... I'm not 100% convinced
that uClinux required quartus installed to build...)


-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2009-10-06 15:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  9:17 Øyvind Harboe
2009-10-06 13:34 ` Alex Schuilenburg
2009-10-06 14:31   ` Øyvind Harboe
2009-10-06 15:06     ` Alex Schuilenburg
2009-10-06 15:19       ` Øyvind Harboe
2009-10-06 16:04         ` Alex Schuilenburg
2009-10-06 14:37   ` Edgar Grimberg
2009-10-06 15:12     ` Alex Schuilenburg
2009-10-06 15:26     ` Øyvind Harboe [this message]
2009-10-07  0:29       ` Jonathan Larmour
2009-10-07  5:31         ` Øyvind Harboe
2009-10-07 14:34           ` [ECOS] " Grant Edwards
2009-10-07 16:31             ` Paul D. DeRocco
2009-10-07 18:30               ` Grant Edwards
2009-10-07 23:10           ` [ECOS] " Alex Schuilenburg
2009-10-08  0:31             ` Paul D. DeRocco
2009-10-08 13:20               ` Alex Schuilenburg

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=c09652430910060826u1dbb0c4cj43434107ccae1cfd@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=alexs@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=edgar.grimberg@zylin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).