On Tue, 30 Nov 2010, Pavel Machek wrote:
On Tue 2010-11-30 11:30:18, Luis R. Rodriguez wrote:
On Tue, Nov 30, 2010 at 11:26 AM, Pavel Machek <pavel@xxxxxx> wrote:
Hi!
everything else can be independent code. For ath9k in particular this
means we keep ath9k_hw shared between our Operating Systems and that's
it. In addition to this I believe opening up the common drivers for
The Linux copy needs to be GPL,
GPL-Compatible you mean, right. I mean we have ath9k_hw with
permissive licensed files.
GPL-compatible is not right word. It has to be either GPL, or so
permissive that anyone is allowed to turn it into GPL.
Oh?
Kernel is GPL. Dual BSD/GPL is ok. Just BSD... I don't think so.
/*
* Copyright (c) 2008 Atheros Communications Inc.
*
* Permission to use, copy, modify, and/or distribute this software
for any
* purpose with or without fee is hereby granted, provided that the
above
* copyright notice and this permission notice appear in all copies.
*
...but I need permission to relicense it under GPL, and I'm not sure I
have it.
Pavel
unless it's the old 4-clause BSD license (with the advertising clause,
which almost nobody used anymore), the BSD code can be relicensed as
anything (including proprietary), as long as the notices in the file are
maintained.
it doesn't take more explicit permission to re-license something as GPL
than it does to make it closed-source.
However,
there are quite a few files in the kernel that are BSD licensed, when
combined with other GPL code, the only way you can re-distribute the
result is under the GPL, so it is effectivly 'converted' when you compile,
but by leaving the file BSD, improvements to it can be shared back with
the original authors and put into their main codebase, so it's actually
more polite to leave the license as-is for this file.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
