linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: bkuhn@ebb.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Greg KH <greg@kroah.com>, David Miller <davem@davemloft.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	Charles Marker <Charles.Marker@atheros.com>,
	Jouni Malinen <Jouni.Malinen@atheros.com>,
	Kevin Hayes <kevin@atheros.com>,
	Zhifeng Cai <zhifeng.cai@atheros.com>,
	Don Breslin <Don.Breslin@atheros.com>,
	Doug Dahlby <Doug.Dahlby@atheros.com>,
	Julia Lawall <julia@diku.dk>
Subject: Re: Challenges with doing hardware bring up with Linux first
Date: Tue, 30 Nov 2010 21:00:19 +0100	[thread overview]
Message-ID: <20101130200019.GA28735@elf.ucw.cz> (raw)
In-Reply-To: <AANLkTinMyAeVJJc7Lc-vt_Ywr+vcSf-GAiQwggTGbqh8@mail.gmail.com>

On Tue 2010-11-30 11:30:18, Luis R. Rodriguez wrote:
> On Tue, Nov 30, 2010 at 11:26 AM, Pavel Machek <pavel@ucw.cz> 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

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2010-11-30 20:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  8:46 Challenges with doing hardware bring up with Linux first Luis R. Rodriguez
2010-11-18 11:11 ` Theodore Tso
2010-11-18 16:46   ` Luis R. Rodriguez
2010-11-21 13:02     ` Ted Ts'o
2010-11-21 17:29       ` Greg KH
2010-11-21 19:51         ` Luis R. Rodriguez
2010-11-21 20:31           ` Alan Cox
2010-11-21 21:44             ` Ted Ts'o
2010-11-21 21:47               ` Gábor Stefanik
2010-11-21 21:50                 ` Luis R. Rodriguez
2010-11-22  1:00                   ` Greg KH
2010-11-21 23:35                 ` Ted Ts'o
2010-11-21 21:49               ` Luis R. Rodriguez
2010-12-03 14:13               ` Pavel Machek
2010-11-21 21:47             ` Luis R. Rodriguez
2010-11-21 22:12               ` Luis R. Rodriguez
2010-11-18 11:34 ` Alan Cox
2010-11-18 16:51   ` Luis R. Rodriguez
2010-11-30 19:26     ` Pavel Machek
2010-11-30 19:30       ` Luis R. Rodriguez
2010-11-30 19:41         ` Luis R. Rodriguez
2010-11-30 20:00         ` Pavel Machek [this message]
2010-11-30 20:09           ` Luis R. Rodriguez
2010-11-30 20:13           ` david
2010-12-01 16:02             ` Bradley M. Kuhn
2010-11-18 16:45 ` Greg KH
2010-11-18 16:53   ` Luis R. Rodriguez
2010-11-18 17:23     ` Stephen Hemminger
2010-11-21  0:32     ` Adrian Chadd
2010-11-21  5:53       ` Luis R. Rodriguez
2010-11-21  7:11         ` Adrian Chadd

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=20101130200019.GA28735@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Charles.Marker@atheros.com \
    --cc=Don.Breslin@atheros.com \
    --cc=Doug.Dahlby@atheros.com \
    --cc=Jouni.Malinen@atheros.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bkuhn@ebb.org \
    --cc=davem@davemloft.net \
    --cc=greg@kroah.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=julia@diku.dk \
    --cc=kevin@atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=shemminger@vyatta.com \
    --cc=zhifeng.cai@atheros.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;
as well as URLs for NNTP newsgroup(s).