From: Alexander Fisher <alexjfisher@gmail.com>
To: Michael Buesch <mbuesch@freenet.de>
Cc: "Jeff V. Merkey" <jmerkey@utah-nac.org>, linux-kernel@vger.kernel.org
Subject: Re: Would I be violating the GPL?
Date: Tue, 1 Nov 2005 20:46:11 +0000 [thread overview]
Message-ID: <5449aac20511011246r6ece9f18rb3b7353dbfc2dedb@mail.gmail.com> (raw)
In-Reply-To: <200511012012.32995.mbuesch@freenet.de>
On 11/1/05, Michael Buesch <mbuesch@freenet.de> wrote:
> 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.
I've got the source code to the device firmware too. So despite the
fact the driver has been written in c++, it might be possible to write
a usable specification. This isn't something I want to do. I'd
imagine this sort of action can really ruin a supplier/customer
relationship. What good is a GPLed driver if no one is prepared to
sell you the hardware?
So if the conclusion is that the driver can't be distributed under
anything other than the GPL (further opinions/confirmations welcome),
I think I've got two options. Find a different hardware vendor or
convince the current supplier to relicense their code.
I'm hoping that the opinions from one or two major linux kernel
copyright holders will help me in convincing them to do this.
Thanks,
Alex
next prev parent reply other threads:[~2005-11-01 20:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 17:49 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
2005-11-01 20:46 ` Alexander Fisher [this message]
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
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=5449aac20511011246r6ece9f18rb3b7353dbfc2dedb@mail.gmail.com \
--to=alexjfisher@gmail.com \
--cc=alex@alexfisher.me.uk \
--cc=jmerkey@utah-nac.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.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
all inboxes | Powered by JetHome®