From: "Dave Neuer" <mr.fred.smoothie@pobox.com>
To: "Phillip Susi" <psusi@cfl.rr.com>
Cc: Luke-Jr <luke@dashjr.org>, "Anshuman Gholap" <anshu.pg@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [future of drivers?] a proposal for binary drivers.
Date: Thu, 9 Mar 2006 12:33:24 -0500 [thread overview]
Message-ID: <161717d50603090933o3df190f9vb1e06b0ec37deb8e@mail.gmail.com> (raw)
In-Reply-To: <441057D4.6030304@cfl.rr.com>
On 3/9/06, Phillip Susi <psusi@cfl.rr.com> wrote:
> Luke-Jr wrote:
> > Or Linux can remain GPL'd, which prohibits binary drivers *legally*, and back
> > this by keeping a non-stable API which prohibits binary drivers
> > *technically*.
>
> If binary drivers are illegal, then why have ATI and nvidia not been
> sued yet?
Because no sufficiently deep-pocketed plaintiff has chosen to do so
yet. Don't incorrectly infer anything about the existence of a cause
of action from a lack of legal proceedings so far.
>
> Interacting with the kernel does not make your software a derived work.
That may or may not be true, depending on the nature of the
interaction, and the arbiter of truth in this case is the court
system, not you or I.
> A derived work is if you make your own kernel that is very close to a
> straight copy of the Linux kernel. The right to create new works that
> interact with others ( and therefore, require some understanding of how
> the other work operates ) is specifically protected by the US copyright
> act.
There are no dearth of legal opinions on this matter which differ
quite radically from your interpretation here, quite a few from
lawyers. As far as I am concerned (and the GPL too, if my
interpretation of it is correct), any code is a derived work of my
code if either a) it directly makes use of symbols in my code or b) it
cannot execute unless my code executes, such that its distribution
without my code would be useless.
>
> This is why it is legal to reverse engineer a binary driver to gain an
> understanding of how the hardware operates, publish that information,
> and then use that information to create new software to operate that
> hardware.
No, you are referring to a restriction on the limitations in software
licenses which is separate from copyright. Copyright law does not talk
about interoperability at all. And even the applicability of the
restriction to which you refer is jurisdiction-dependant as well as
context-dependant (see the DMCA).
Regards,
Dave
next prev parent reply other threads:[~2006-03-09 17:33 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 9:35 Anshuman Gholap
2006-03-08 9:51 ` Jan Knutar
2006-03-08 10:03 ` Anshuman Gholap
2006-03-08 10:23 ` Martin Mares
2006-03-08 14:34 ` Jan Engelhardt
2006-03-08 11:11 ` Jan Knutar
2006-03-08 13:07 ` Diego Calleja
2006-03-09 15:17 ` Luke-Jr
2006-03-09 16:22 ` Phillip Susi
2006-03-09 16:56 ` Michael Concannon
2006-03-09 9:21 ` Helge Hafting
2006-03-10 8:03 ` Matthias Andree
2006-03-13 23:06 ` Bernd Petrovitsch
2006-03-14 0:00 ` David Schwartz
2006-03-15 0:50 ` Valdis.Kletnieks
2006-03-15 9:18 ` Bernd Petrovitsch
2006-03-08 19:41 ` Martin Michlmayr
2006-03-08 9:57 ` Xavier Bestel
2006-03-08 10:27 ` Al Viro
2006-03-08 10:52 ` Anshuman Gholap
2006-03-08 10:55 ` Arjan van de Ven
2006-03-08 11:02 ` Anshuman Gholap
2006-03-14 3:02 ` Jon Masters
[not found] ` <20060313223520.113bc6d0.seanlkml@sympatico.ca>
2006-03-14 3:35 ` sean
2006-03-08 11:40 ` Matthias Schniedermeyer
2006-03-08 12:00 ` Anshuman Gholap
2006-03-09 15:32 ` Rik van Riel
2006-03-08 14:59 ` Dave Neuer
2006-03-08 21:54 ` Hannu Savolainen
2006-03-09 4:41 ` David Schwartz
2006-03-09 10:02 ` Dave Airlie
2006-03-09 10:42 ` Rudolf Randal
2006-03-09 11:22 ` DervishD
2006-03-09 12:13 ` Andreas Mohr
2006-03-09 18:34 ` Alistair John Strachan
2006-03-10 8:19 ` DervishD
2006-03-09 22:04 ` David Schwartz
2006-03-09 11:41 ` Dagfinn Ilmari Mannsåker
2006-03-09 22:12 ` David Schwartz
2006-03-09 15:13 ` Dave Neuer
2006-03-09 22:11 ` David Schwartz
2006-03-09 23:30 ` Dave Neuer
2006-03-10 1:04 ` David Schwartz
2006-03-09 9:26 ` Helge Hafting
2006-03-09 15:09 ` Luke-Jr
2006-03-09 16:29 ` Phillip Susi
2006-03-09 16:49 ` Olivier Galibert
2006-03-09 17:33 ` Dave Neuer [this message]
2006-03-09 18:25 ` Xavier Bestel
2006-03-09 20:22 ` Dave Neuer
2006-03-09 21:32 ` marty fouts
2006-03-11 0:54 ` Eduard Bloch
2006-03-11 1:01 ` Jan Knutar
2006-03-11 9:16 ` DervishD
2006-03-11 9:52 ` Eduard Bloch
2006-03-11 11:43 ` David Schwartz
2006-03-11 12:07 ` DervishD
2006-03-12 17:09 ` Dave Neuer
2006-03-13 2:19 ` David Schwartz
2006-03-13 16:16 ` Dave Neuer
2006-03-13 21:57 ` David Schwartz
2006-03-14 13:30 ` Helge Hafting
2006-03-12 3:57 ` Dave Neuer
2006-03-13 5:16 ` David Schwartz
2006-03-13 5:25 ` David Schwartz
2006-03-13 8:20 ` Arjan van de Ven
2006-03-13 21:57 ` David Schwartz
[not found] ` <20060314032447.6be9af0a.seanlkml@sympatico.ca>
2006-03-14 8:24 ` sean
2006-03-14 10:46 ` David Schwartz
2006-03-14 21:42 ` Valdis.Kletnieks
2006-03-13 9:24 ` Bernd Petrovitsch
2006-03-13 17:16 ` Lee Revell
2006-03-13 22:08 ` Bernd Petrovitsch
2006-03-13 21:57 ` David Schwartz
2006-03-09 20:15 ` Phillip Susi
2006-03-09 21:30 ` Dave Neuer
2006-03-09 22:06 ` Lee Revell
2006-03-10 2:57 ` Phillip Susi
2006-03-10 4:25 ` David Schwartz
2006-03-09 22:21 ` David Schwartz
2006-03-08 21:28 Tim Tassonis
2006-03-08 21:32 ` Randy.Dunlap
2006-03-09 0:20 ` Jan Knutar
2006-03-13 11:17 ` Helge Hafting
2006-03-13 15:19 ` Anshuman Gholap
2006-03-13 15:53 ` Dave Neuer
2006-03-13 6:02 Matt Reuther
2006-03-13 9:08 ` Bernd Petrovitsch
2006-03-13 22:00 ` David Schwartz
2006-03-13 22:32 ` Lee Revell
2006-03-14 0:02 ` David Schwartz
2006-03-13 19:00 Tim Tassonis
2006-03-13 19:15 ` Lee Revell
2006-03-13 19:25 ` Tim Tassonis
2006-03-13 19:31 ` Lee Revell
2006-03-13 19:46 ` Tim Tassonis
2006-03-13 23:06 ` Bernd Petrovitsch
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=161717d50603090933o3df190f9vb1e06b0ec37deb8e@mail.gmail.com \
--to=mr.fred.smoothie@pobox.com \
--cc=anshu.pg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@dashjr.org \
--cc=psusi@cfl.rr.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
all inboxes | Powered by JetHome®