public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Alternative License for Parts of MTD?
Date: Fri, 13 Apr 2012 18:28:46 +0300	[thread overview]
Message-ID: <1334330926.2544.88.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4F883513.4000301@embedded-brains.de>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On Fri, 2012-04-13 at 16:15 +0200, Sebastian Huber wrote:
> Hello,
> 
> I work with the real-time operating system RTEMS (http://www.rtems.com).  The 
> license of this system is GPL with an exception that allows static linking 
> without restrictions:
> 
> http://www.rtems.com/license/LICENSE
> 
> This is very similar to the eCos license:
> 
> http://ecos.sourceware.org/license-overview.html
> 
> RTEMS has currently no framework for flash devices.  It would be nice if we can 
> use parts of the MTD system, e.g. the header files and device independent 
> support routines like "drivers/mtd/nand/nand_base.c".  Is it possible to 
> release parts of the MTD code under the RTEMS or eCos license, or would you 
> categorically refuse this?

Irrespectively of what random people in the mailing list think, this is
a question to layers. And I guess you'd need to have permission of all
copyright holders, which I guess all people who contributed, and this is
practically impossible to do. But I do not know for sure whether this is
correct or not :-)

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-04-13 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 14:15 Alternative License for Parts of MTD? Sebastian Huber
2012-04-13 14:44 ` Richard Weinberger
2012-04-13 14:50   ` Sebastian Huber
2012-04-13 15:28 ` Artem Bityutskiy [this message]
2012-04-16 13:32   ` Atlant Schmidt

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=1334330926.2544.88.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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