From: "David Schwartz" <davids@webmaster.com>
To: linux-kernel@vger.kernel.org
Subject: Re: License violation?
Date: Fri, 02 Mar 2007 13:18:09 -0800 [thread overview]
Message-ID: <WorldClient-F200703021318.AA18090017@webmaster.com> (raw)
In-Reply-To: <45E76C16.1030706@gmail.com>
> I have a GPL driver (written by me) with workarounds, since I hadn't
> know-how,
> when I wrote it. Now I've got 2.4 proprietary driver from the vendor.
> Is use of
> the 2.4 driver know-how OK? (And could be such driver merged?)
Unless you made some kind of agreement with the copyright holder or did
not lawfully acquire the software, you have every right to study it and
learn from it. You have every right to use your own knowledge to implement
a driver any way you want.
What you can't do, of course, is steal protected expression from the
driver. Function is not protected. Facts are not protected.
DS
prev parent reply other threads:[~2007-03-02 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 0:13 License violation? Jiri Slaby
2007-03-02 0:31 ` Jeremy Fitzhardinge
2007-03-02 0:36 ` Jiri Slaby
2007-03-02 0:37 ` Jeremy Fitzhardinge
2007-03-02 1:07 ` Jiri Slaby
[not found] ` <45E77931.5090005@goop.org>
2007-03-02 1:27 ` Jiri Slaby
2007-03-02 12:41 ` Alan
2007-03-02 20:43 ` Jiri Slaby
2007-03-02 21:18 ` David Schwartz [this message]
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=WorldClient-F200703021318.AA18090017@webmaster.com \
--to=davids@webmaster.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox