All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: "Jeff V. Merkey" <jmerkey@utah-nac.org>
Cc: alex@alexfisher.me.uk, linux-kernel@vger.kernel.org
Subject: Re: Would I be violating the GPL?
Date: Tue, 1 Nov 2005 20:12:32 +0100	[thread overview]
Message-ID: <200511012012.32995.mbuesch@freenet.de> (raw)
In-Reply-To: <4367A990.2040301@utah-nac.org>

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

On Tuesday 01 November 2005 18:44, you wrote:
> No, don't take the code without the suppliers permission. 

I interpreted his text as if he already has permission to use the code.

> It contains  
> trade secrets and you can get into a ot of trouble if there's an 
> agreement between the two of you.  Contact the supplier.  Tell them to 
> abstract away thre kernel headers, or rewrite to remove them, or grant 
> you persmission to open source the driver.

I did not say he should open source the driver. That will give trouble.
I suggested to write a _device_ specification. Driver specific things do not
care.

> The UK is the land of  
> frivilous lawsuits (I should know a lot about this :-)  ), so don;t 
> expose yourself and breach any agreements. 

Sure.

> Jeff
> 
> 
> Michael Buesch wrote:
> 
> >On Tuesday 01 November 2005 18:49, Alexander Fisher wrote:
> >  
> >
> >>Hello.
> >>
> >>A supplier of a PCI mezzanine digital IO card has provided a linux 2.4
> >>driver as source code.  They have provided this code source with a
> >>license stating I won't redistribute it in anyway.
> >>My concern is that if I build this code into a module, I won't be able
> >>to distribute it to customers without violating either the GPL (by not
> >>distributing the source code), or the proprietary source code license
> >>as currently imposed by the supplier.
> >>From what I have read, this concern is only valid if the binary module
> >>is considered to be a 'derived work' of the kernel.  The module source
> >>directly includes the following kernel headers :
> >>    
> >>
> >
> >Take the code and write a specification for the device.
> >Should be fairly easy.
> >Someone else will pick up the spec and write a clean GPLed driver.
> >
> >Like these, without the reverse engineering part:
> >http://en.wikipedia.org/wiki/Clean_room_design
> >http://en.wikipedia.org/wiki/Chinese_wall#Computer_science
> >
> >  
> >
> 
> 
> 

-- 
Greetings Michael.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-11-01 19:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 17:49 Would I be violating the GPL? Alexander Fisher
2005-11-01 16:43 ` Jeff V. Merkey
2005-11-01 19:15   ` Alistair John Strachan
2005-11-16 15:26     ` David Schwartz
2005-11-16 16:39       ` Jeffrey V. Merkey
2005-11-01 20:32   ` Rob Landley
2005-11-01 20:46   ` Arjan van de Ven
2005-11-01 19:00 ` Michael Buesch
2005-11-01 17:44   ` Jeff V. Merkey
2005-11-01 19:12     ` Michael Buesch [this message]
2005-11-01 20:46       ` Alexander Fisher
2005-11-01 21:06         ` linux-os (Dick Johnson)
2005-11-02  9:49         ` Giuliano Pochini
2005-11-02 14:54           ` Alex Lyashkov
2005-11-02 15:29             ` Nix
2005-11-02 15:42               ` Alex Lyashkov
2005-11-02 16:16               ` linux-os (Dick Johnson)
2005-11-02 17:26                 ` Nix
2005-11-02 15:55             ` Giuliano Pochini
2005-11-10 19:02           ` Jan Engelhardt
2005-11-10 19:12             ` Lennart Sorensen
2005-11-17 21:23               ` Jan Engelhardt
2005-11-18 15:19                 ` Lennart Sorensen
2005-11-18 15:25                   ` Jan Engelhardt
2005-11-18 21:55                   ` Petr Vandrovec
2005-11-01 22:04     ` Rob Landley
2005-11-01 19:58   ` Lee Revell
2005-11-01 20:30     ` Jeff V. Merkey
2005-11-01 20:57     ` Alexander Fisher
2005-11-02 16:12 ` Stuart MacDonald
2005-11-03 12:44 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 22:21 linux
2005-11-02 22:47 ` linux-os (Dick Johnson)
2005-11-03  3:50 ` Rob Landley
2005-11-04  0:57   ` Horst von Brand

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=200511012012.32995.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=alex@alexfisher.me.uk \
    --cc=jmerkey@utah-nac.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.