From: Denis Vlasenko <vda.linux@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Subject: Re: ACX100 (softmac-based) driver ready to merge, but is it legal?
Date: Thu, 6 Jul 2006 19:29:49 +0200 [thread overview]
Message-ID: <200607061929.49103.vda.linux@gmail.com> (raw)
In-Reply-To: <20060629142643.GA24463@tuxdriver.com>
On Thursday 29 June 2006 16:26, John W. Linville wrote:
> I apologize for the long copy list. I have tried to include all
> known interested parties.
>
> This is a follow-up to a thread started by Andrew a few weeks ago
> about what should be merged for 2.6.18. One of the topics he cited
> was the ACX100 driver which he has carried in -mm for quite some time.
> I have a slightly different (softmac based) version of that driver
> in wireless-2.6 which I think is worth merging now.
>
> In the aforementioned thread, some questions were raised about the
> legality of the ACX100 driver (i.e. tiacx) code base, but no one
> had any specific points other than that it is not 100% "clean room"
> derived. Others point-out that this is not strictly a requirement.
> The matter dropped without a strong defense from the tiacx team.
>
> I hereby invite the tiacx team to defend their work by making public,
> affirmative statements indicating a) how they produced their code; and,
> b) that they have the legal right to license it as part of the Linux
> kernel under the GPL. As an incentive to this, I have already made
> the necessary preparations for this driver to be merged immediately.
About the part of the acx code which was done by me:
I was working upon the already existing acx driver.
I do not know how it was developed before I started to play with it,
but I certainly never worked for TI and did not receive any code
or documents from TI (I was asking for the documentation,
but there was no answer).
I realize that this info is not enough to determine whether tiacx
driver is "clean" legalese-wise.
--
vda
prev parent reply other threads:[~2006-07-06 17:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060604135011.decdc7c9.akpm@osdl.org>
2006-06-05 1:06 ` wireless (was Re: 2.6.18 -mm merge plans) Jeff Garzik
2006-06-05 1:15 ` Andrew Morton
2006-06-05 8:33 ` Andreas Mohr
2006-06-05 8:45 ` Arjan van de Ven
2006-06-05 10:26 ` Alan Cox
2006-06-05 10:35 ` Arjan van de Ven
2006-06-05 10:59 ` Alan Cox
2006-06-10 6:58 ` Pavel Machek
2006-06-05 8:54 ` Christoph Hellwig
2006-06-05 12:33 ` Jeff Garzik
2006-06-05 12:48 ` Arjan van de Ven
2006-06-05 12:52 ` Jeff Garzik
2006-06-05 14:02 ` Linux kernel and laws Adrian Bunk
2006-06-05 14:21 ` linux-os (Dick Johnson)
2006-06-06 5:33 ` Evgeniy Polyakov
2006-06-05 13:27 ` wireless (was Re: 2.6.18 -mm merge plans) John W. Linville
2006-06-05 13:31 ` Christoph Hellwig
2006-06-05 13:42 ` Arjan van de Ven
2006-06-05 16:24 ` Alan Cox
2006-06-29 14:26 ` ACX100 (softmac-based) driver ready to merge, but is it legal? -- " John W. Linville
[not found] ` <20060629144233.GB24463@tuxdriver.com>
2006-06-29 14:47 ` [Acx100-users] Denis Vlasenko, where are you? (mail bounced) Andreas Mohr
2006-07-06 17:29 ` Denis Vlasenko [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=200607061929.49103.vda.linux@gmail.com \
--to=vda.linux@googlemail.com \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=jeff@garzik.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).