linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: David Jander <david.jander@protonic.nl>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: problems on isp1362 driver
Date: Mon, 20 Jun 2005 21:25:39 +0200	[thread overview]
Message-ID: <20050620192544.97393C1510@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 20 Jun 2005 12:38:18 +0200." <200506201238.19121.david.jander@protonic.nl>

In message <200506201238.19121.david.jander@protonic.nl> you wrote:
>
> 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, 

No, you cannot even do that. The Philips license explicitely  forbids
to  "combine Open Source Software with the Software or any derivative
work thereof". This effectively prevents any use of the driver  in  a
Linux  environment. Of course you can now ask which sense it makes to
release a Linux driver under such a license, but please don't ask me.
Ask the id^H^Hlawyers at Philips.

> 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.

Please read again. This is allowed only for  pre-existing  code  that
was not written for Linux. And even then it's not really clean. BUt I
seriously doubt that the Philips Linux driver can claim to fall under
this exception.

My interpretation is that an anal-restrictive lawyer came up  with  a
license  once,  and  some  other people applied this license to Linux
drivers without any thinking. If you want to  complain,  complain  at
Philips.  Alternatively,  just  don't  use  their code. If necessary,
don't use their hardware  either.  There  are  other  solutions  with
better software support.

> 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 :-(

100% ACK from me.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
All your people must learn before you can reach for the stars.
	-- Kirk, "The Gamesters of Triskelion", stardate 3259.2

  reply	other threads:[~2005-06-20 19:25 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
2005-06-20 19:25     ` Wolfgang Denk [this message]
  -- 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=20050620192544.97393C1510@atlas.denx.de \
    --to=wd@denx.de \
    --cc=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).