From: David Jander <david.jander@protonic.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: problems on isp1362 driver
Date: Mon, 20 Jun 2005 12:38:18 +0200 [thread overview]
Message-ID: <200506201238.19121.david.jander@protonic.nl> (raw)
In-Reply-To: <20050617191231.B23C0C1510@atlas.denx.de>
On Friday 17 June 2005 21:12, Wolfgang Denk wrote:
> in message <000001c57347$04a45d00$07070a0a@luj> you wrote:
> > We are using Philips ISP1362 usb controller on our ppc-embedded system.
> > We have ported the phlips's driver, PHCI, to ppc. The Philips linux
> > driver is that of 2002.
>
> You cannot do that. The Philips driver comes uner a proprietary
> license which is incompatible with the GPL. You must not use their
> driver in the context of a Linux kernel or any other GPLed software.
> You are either violating the GPL, or the Philips license. Be
> careful!!!
IANAL, but I think theoretically at least, it should be possible, if you
manage to craft sort of a "GPL abstraction layer" around the philips driver,
to shield it from "GPL influence" in the kernel, just like Nvidia and others
do. To the letter of the GPL that is not possible, but AFAIK the linux kernel
license grants an exception that permits binary-only drivers for instance.
Anyway, it probably is a bad and dangerous idea to try to pull this off. As
for me, I decided it is much safer to stay as far away as possible from the
philips source. Looking at it could be fatal for an OSS-coder like me (my
eyes could get poisoned).
Here goes a big "BOOOO" to Philips for doing this in the first place :-(
Greetings,
--
David Jander
next prev parent reply other threads:[~2005-06-20 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 14:15 problems on isp1362 driver lu
2005-06-17 19:12 ` Wolfgang Denk
2005-06-20 10:38 ` David Jander [this message]
2005-06-20 19:25 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-07-15 0:14 David Zhang
2005-11-07 7:27 ` David Jander
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=200506201238.19121.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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 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).