From: George Michaelson <ggm@apnic.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: forsyth@terzarima.net
Subject: Re: [9fans] Native vs Emulated
Date: Tue, 8 Mar 2005 17:37:07 -0600 [thread overview]
Message-ID: <20050308173707.01d5c668@garlique> (raw)
In-Reply-To: <026cbb59bf5922249b10c565ea9d8059@terzarima.net>
the X31 I am on in NetBSD has atheros drivers, which I think may be sam
leffler's work in both Free and NetBSD. It uses the binary only HAL code.
is there some codebase outside of the HAL stuff?
-G
---
$NetBSD$
$Id: README,v 1.2 2004/05/15 22:26:25 samleffler Exp $
WARNING: THIS IS A BETA DISTRIBUTION. THIS SOFTWARE HAS KNOWN PROBLEMS AND
WARNING: LIMITATIONS THAT WILL BE CORRECTED BEFORE A PRODUCTION RELEASE.
WARNING: USE AT YOUR OWN RISK!
Atheros Hardware Access Layer (HAL)
===================================
* Copyright (c) 2002-2004 Sam Leffler.
* Copyright (c) 2002-2004 Atheros Communications, Inc.
* All rights reserved.
Read the file COPYRIGHT for the complete copyright.
This code manages much of the chip-specific operation of the Atheros
driver. The HAL is provided in a binary-only form in order to comply with
FCC regulations. In particular, a radio transmitter can only be operated
at power levels and on frequency channels for which it is approved. The
FCC requires that a software-defined radio cannot be configured by a user
to operate outside the approved power levels and frequency channels.
This makes it difficult to open-source code that enforces limits on
the power levels, frequency channels and other parameters of the radio
transmitter. See
http://ftp.fcc.gov/Bureaus/Engineering_Technology/Orders/2001/fcc01264.pdf
for the specific FCC regulation. Because the module is provided in a
binary-only form it is marked "Proprietary"; this means when you load
it you will see messages that your system is now "tainted".
If you wish to use this driver on a platform for which an ath_hal
module is not already provided please contact the author. Note that
this is only necessary for new _architectures_; the HAL is not tied to
any specific version of your operating system.
:
:
:
next prev parent reply other threads:[~2005-03-08 23:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 16:10 John Stalker
2005-03-04 16:52 ` Ronald G. Minnich
2005-03-05 11:25 ` John Stalker
2005-03-07 2:25 ` Ronald G. Minnich
2005-03-07 2:58 ` Russ Cox
2005-03-07 10:10 ` Gorka Guardiola
2005-03-07 15:40 ` Brantley Coile
2005-03-07 15:59 ` Ronald G. Minnich
2005-03-07 17:10 ` Fco. J. Ballesteros
2005-03-08 4:20 ` Martin C.Atkins
2005-03-08 14:18 ` Ronald G. Minnich
2005-03-08 23:13 ` Charles Forsyth
2005-03-08 23:16 ` Ronald G. Minnich
2005-03-08 23:19 ` Charles Forsyth
2005-03-08 23:37 ` George Michaelson [this message]
2005-03-08 23:19 ` George Michaelson
2005-03-08 23:27 ` Ronald G. Minnich
2005-03-08 23:29 ` Charles Forsyth
2005-03-09 0:06 ` Andrew Simmons
2005-03-09 5:33 ` Martin C.Atkins
2005-03-09 12:07 ` Gorka Guardiola
2005-03-09 15:43 ` Martin C.Atkins
2005-03-09 16:20 ` George Michaelson
2005-03-09 17:00 ` Steve Simon
2005-03-09 17:01 ` Steve Simon
2005-03-09 17:36 ` [9fans] Native vs Emulated (OT) Leo Caves
2005-03-09 0:23 [9fans] Native vs Emulated Skip Tavakkolian
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=20050308173707.01d5c668@garlique \
--to=ggm@apnic.net \
--cc=9fans@cse.psu.edu \
--cc=forsyth@terzarima.net \
/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).