linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Marco Stornelli <marco.stornelli@coritel.it>,
	Joe MacDonald <joe.macdonald@gmail.com>,
	linux-embedded@vger.kernel.org
Subject: Re: Fwd: Some embedded topics
Date: Sun, 1 Jun 2008 19:09:16 -0500	[thread overview]
Message-ID: <200806011909.17326.rob@landley.net> (raw)
In-Reply-To: <48407DE5.3000208@am.sony.com>

On Friday 30 May 2008 17:21:25 Tim Bird wrote:
> Marco Stornelli wrote:
> > There's a MontaVista patent on PRAMFS and I think that most of times
> > when a company hears this thing it skips quickly this solution.
>
> Hmmm.  I don't recall anything about a patent on PRAMFS.
>
> There are lots of issues here, but I think it's OK to use.
> At a minimum,  MontaVista's PRAMFS was submitted to the CE Linux Forum
> in an older kernel (2.4.20-based).  MontaVista was well-aware
> of this submission (although it did not come directly from them).
> MV was under an IP agreement with CELF which required them to
> disclose such patents to the forum, and none was received.
>
> In any event (and without wanting to start a large off-topic legal
> thread here), some lawyers would interpret the knowing publication
> of an implementation embodying a patent under the GPL to be an
> implicit license of use for the patent.

Yup.  Although IBM and Red Hat make this license explicit: you may use (at 
least some of) their patents in code licensed under the terms of GPLv2.  I 
don't know if MontaVista has an explicit license statement or not.

IBM licensed the RCU patents as a condition of the code getting merged into 
Linux, and Red Hat's patent policy is here:
http://www.redhat.com/legal/patent_policy.html

More recently, they all joined the "open invention network" which is a 
mutually assured destruction patent pool thingy:

http://www.ibm.com/news/us/en/2005/11/2005_11_10.html
http://arstechnica.com/news.ars/post/20070807-google-signs-on-with-open-invention-network.html

Beyond all that, there's a legal theory (as yet untested in court) that taking 
patent enforcement action against GPLv2 code is grounds for any copyright 
holder in the GPL project to terminate _your_ right to use that code, because 
it's a direction violation of GPLv2 clause 6 forbidding additional 
restrictions on recipients exercise of rights.  (Fairly straightforward 
argument, really.)

That hasn't been tested in court, and attempts to do so could easily drag on 
for quite a while.  The end result could easily be "nobody can legally 
distribute the version that violates the patent, including the patentholder" 
since GPLv2 is designed to break closed.

I neither know nor care about GPLv3.  (As with vogon grandmothers, "In brief: 
avoid.")

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  reply	other threads:[~2008-06-02  0:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <483C83DE.3040604@cisco.com>
     [not found] ` <483C83DE.3040604-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2008-05-29  2:09   ` Some embedded topics Paul Gortmaker
     [not found] ` <8bd0f97a0805271527i622a31b8t68ba24c80a2e034a@mail.gmail.com>
     [not found]   ` <20080527223142.GU26837@email.mot.com>
     [not found]     ` <20080527223142.GU26837-qbu1+ugcRq/by3iVrkZq2A@public.gmane.org>
2008-05-29  3:01       ` Rob Landley
     [not found]         ` <200805282201.48746.rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2008-05-29  4:21           ` Mike Frysinger
     [not found]             ` <8bd0f97a0805282121j10a99bb7ve92efc6a8dc8bbb1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-29  5:38               ` Wolfgang Denk
2008-05-29 17:31             ` Rob Landley
2008-05-29 18:20               ` Mike Frysinger
2008-05-29  5:34           ` Wolfgang Denk
2008-05-29  9:31         ` Geert Uytterhoeven
2008-05-30 22:59           ` Tim Bird
2008-05-30 23:20             ` Jordan Crouse
2008-05-31  0:07             ` Josh Boyer
2008-05-31 13:32             ` Geert Uytterhoeven
     [not found]     ` <8bd0f97a0805271535w267be51fq669def9aa424e4e7@mail.gmail.com>
     [not found]       ` <840404080805280740q4486f377x49c106e20d9f5dc2@mail.gmail.com>
     [not found]         ` <840404080805280744t351da73fk885fa7b29c05659c@mail.gmail.com>
     [not found]           ` <483D7355.5050803@coritel.it>
     [not found]             ` <483D7355.5050803-5RgZt0ZUL+KonA0d6jMUrA@public.gmane.org>
2008-05-28 15:44               ` Fwd: " Joe MacDonald
2008-05-30 22:21             ` Tim Bird
2008-06-02  0:09               ` Rob Landley [this message]
2008-06-03  8:32               ` Marco Stornelli
     [not found] ` <20080527173118.12ec691b@vader.jdub.homelinux.org>
     [not found]   ` <f608b67d0805271537m1b07e08y5dd84f7bbd8918cf@mail.gmail.com>
     [not found]     ` <20080527180200.56ffc588@vader.jdub.homelinux.org>
2008-05-30 22:36       ` Tim Bird
2008-05-31  0:04         ` Josh Boyer
2008-06-01 23:52           ` Rob Landley

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=200806011909.17326.rob@landley.net \
    --to=rob@landley.net \
    --cc=joe.macdonald@gmail.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=marco.stornelli@coritel.it \
    --cc=tim.bird@am.sony.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 NNTP newsgroup(s).