linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Pommnitz <pommnitz@yahoo.com>
To: linux-wireless@vger.kernel.org, Reyk Floeter <reyk@openbsd.org>
Subject: Re: request for information about the "ath5k" licensing
Date: Fri, 7 Sep 2007 01:20:53 -0700 (PDT)	[thread overview]
Message-ID: <302924.76562.qm@web51403.mail.re2.yahoo.com> (raw)

Reyk Floeter wrote:
> I'm still waiting for an answer. Your process is taking too long.
> 
> Reyk

Reyk (and everybody else),
I'm writing as a silent observer, not as an involved (until now) party. I will restrict my answer mostly to links to information I consider key facts of this whole affair:

The development of the Linux Atheros driver (both for the official Atheros HAL and your work) takes place at www.madwifi.org. The SVN branch based on openhal can be found here:
http://madwifi.org/browser/branches/ath5k
Going back in the version history you WILL find revisions with the changed license. This mistake has been corrected in revision 2699.

The patches from the openhal team at madwifi.org have been merged into the "official" Linux wireless repository. You can find the branch that includes the ath5k driver here:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=summary
the ath5k files are here:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=tree;f=drivers/net/wireless;h=2d6caeba0924c34b9539960b9ab568ab3d193fc8;hb=everything
(look for the ath5k files). Going back in the revision history you will find, that the proposed license changes where never applied:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-dev.git;a=history;f=drivers/net/wireless/ath5k_hw.c;h=07ad1278b39037caf68825cabcf9469db059dfc8;hb=everything

The mail that started this affair was:
http://marc.info/?l=linux-wireless&m=118831729905625&w=2

If you follow this thread, you will see, that the obvious problems were immediately flagged in the review process.

Next thing: While the proposed change was obviously bad, it *SEEMS* that this was a honest mistake. The following mail
by Sam Leffler suggest, that Jiri Slaby tried to get the consent of the *BSD developers:
http://article.gmane.org/gmane.linux.kernel.wireless.general/5305

Most of the ensuing flame war centered around whether it was illegal to change the license of those dual licensed files. Alan Cox stated in
http://article.gmane.org/gmane.linux.network/70533
"So whats the problem ?"
Theo de Raadt in http://thread.gmane.org/gmane.os.openbsd.misc/127782
wrote "Alan asks "So whats the problem ?".  Well, Alan, I must caution you -- your post is advising people to break the law."

This made a lot of people upset and the whole thing went out of hand.

It was more or less finally settled with the following mail:
http://thread.gmane.org/gmane.linux.kernel.wireless.general/5303

This affair *NEVER* came close to what one would consider the official Linux repository, e.g. Linus tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary

And for Linus' position to BSD vs. GPL in drivers is summarized here:
http://article.gmane.org/gmane.linux.kernel.wireless.general/5452

Kind regards
  Joerg
 
--  
Regards
 
       Joerg
 






      Machen Sie Yahoo! zu Ihrer Startseite. Los geht's: 
http://de.yahoo.com/set

             reply	other threads:[~2007-09-07  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  8:20 Joerg Pommnitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-05 15:18 request for information about the "ath5k" licensing Reyk Floeter
2007-09-05 16:35 ` Michael Buesch
2007-09-05 17:00   ` Luis R. Rodriguez
2007-09-07  6:47     ` Reyk Floeter
2007-09-07 23:42       ` 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=302924.76562.qm@web51403.mail.re2.yahoo.com \
    --to=pommnitz@yahoo.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reyk@openbsd.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).