netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: lwn@lwn.net, madwifi-devel@lists.sourceforge.net
Subject: ANNOUNCE: SFLC helps developers assess ar5k (enabling free Atheros HAL)
Date: Tue, 14 Nov 2006 22:10:26 -0500	[thread overview]
Message-ID: <20061115031025.GH3451@tuxdriver.com> (raw)

It is my pleasure to announce that the SFLC [1] has assisted the ar5k
developers in evaluating the development history of Reyk Floeter's
OpenBSD reverse-engineered Atheros HAL, ar5k [2].  SFLC's assessment
leads to the conclusion that free software developers should not be
worried about using/extending ar5k or porting ar5k to other platforms.

In the past there were serious questions raised and even dire warnings
made about ar5k's copyright status.  The purpose of this statement
is to refute those claims and to publicly clarify ar5k's status
to developers.

SFLC has made independent inquiries with the OpenBSD team regarding the
development history of ar5k source.  The responses received provide
a reasonable basis for SFLC to believe that the OpenBSD developers
who worked on ar5k did not misappropriate code, and that the ar5k
implementation is OpenBSD's original copyrighted work.

This announcement should serve to remove the cloud which has prevented
progress towards an in-kernel driver for Atheros hardware.  This should
be of particular interest to those involved with the DadWifi project [3].

I'd like to take this opportunity to thank the folks at the SFLC for
their hard work, and I'd also like to personally thank Luis Rodriguez
for the role he played in coordinating contact between the SFLC and
the community at large.

Thanks!

John

[1] http://www.softwarefreedom.org/
[2] http://team.vantronix.net/ar5k/
[3] http://marc.theaimsgroup.com/?l=linux-netdev&m=116113064513921&w=2
-- 
John W. Linville
linville@tuxdriver.com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

             reply	other threads:[~2006-11-15  3:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15  3:10 John W. Linville [this message]
2006-11-15 18:42 ` ANNOUNCE: SFLC helps developers assess ar5k (enabling free Atheros HAL) Michael Buesch
2006-11-15 19:21   ` John W. Linville
2006-11-15 19:26     ` Michael Buesch
2006-11-15 19:35       ` Ben Greear
2006-11-16 14:18       ` Jochen Friedrich
2006-11-16 14:56         ` [Madwifi-devel] " Michael Renzmann
2006-11-15 19:26     ` Arjan van de Ven
2006-11-15 19:39     ` [Madwifi-devel] " Pavel Roskin
2006-11-15 20:02       ` Michael Buesch
2006-11-16  5:37         ` Michael Renzmann
2006-11-16 10:07           ` Nick Kossifidis
2006-11-16 11:55             ` Michael Renzmann
2006-11-15 23:28       ` [Madwifi-devel] ANNOUNCE: SFLC helps developers assessar5k " David Kimdon
2006-11-16 14:50       ` [Madwifi-devel] ANNOUNCE: SFLC helps developers assess ar5k " Dan Williams

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=20061115031025.GH3451@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=madwifi-devel@lists.sourceforge.net \
    --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).