From: Jeff Garzik <jgarzik@pobox.com>
To: Ken Schneider <kschneider@bout-tyme.net>
Cc: "Tomita, Haruo" <haruo.tomita@toshiba.co.jp>,
Arjan van de Ven <arjanv@redhat.com>,
"Moore, Eric Dean" <Emoore@lsil.com>,
linux-scsi@vger.kernel.org, "Doelfel, Hardy" <hdoelfel@lsil.com>,
"Mukker, Atul" <Atulm@lsil.com>,
"Jarrett, Peter B." <Peterj@lsil.com>
Subject: Re: new driver
Date: Thu, 19 Feb 2004 00:32:42 -0500 [thread overview]
Message-ID: <40344A7A.5040909@pobox.com> (raw)
In-Reply-To: <1077148668.14308.6.camel@pc1.bout-tyme.net>
Ken Schneider wrote:
> On Wed, 2004-02-18 at 18:39, Tomita, Haruo wrote:
>
>>Hi ken,
>>
>>Eric> There was an effort I started to open source some of
>>Eric> the driver, which was linked to a pre-compiled library.
>>
>>Haruo> The pre-compiled library(megaide_lib.o) is included.
>>
>>Arjan> Then the driver is not available under the terms of the GPL....
>>Arjan> (and not compatible with the kernel license so inclusion is not possible)
>>
>>Ken> And therefore should not any reference to the GPL in the
>>Ken> other files. I think this should be all or nothing.
>>
>>Is it that the source code of megaide_lib.o should be opened?
>
>
> I was told by people on another list that if any part is closed the
> entire package will not be included in the kernel tree. So yes
> negaide.lib.o should be open sourced or LSI should provide drivers to
> linux users as well as any other platform that uses their hardware.
Correct. Drivers must be 100% open source, or they are not included in
Linux.
This is dictated by the GNU General Public License, under which all
kernel code is licensed.
Jeff
next prev parent reply other threads:[~2004-02-19 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 23:39 new driver Tomita, Haruo
2004-02-18 23:57 ` Ken Schneider
2004-02-19 5:32 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 0:27 Doelfel, Hardy
2004-02-18 8:51 Tomita, Haruo
2004-02-18 12:29 ` Arjan van de Ven
2004-02-18 23:29 ` Ken Schneider
2004-02-15 0:06 Ken Schneider
2004-02-15 9:29 ` Christoph Hellwig
2004-02-15 10:57 ` Arjan van de Ven
2004-02-15 20:35 ` Jeff Garzik
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=40344A7A.5040909@pobox.com \
--to=jgarzik@pobox.com \
--cc=Atulm@lsil.com \
--cc=Emoore@lsil.com \
--cc=Peterj@lsil.com \
--cc=arjanv@redhat.com \
--cc=haruo.tomita@toshiba.co.jp \
--cc=hdoelfel@lsil.com \
--cc=kschneider@bout-tyme.net \
--cc=linux-scsi@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