From: insecure <insecure@mail.od.ua>
To: Martin List-Petersen <martin@list-petersen.se>,
"Bryan O'Sullivan" <bos@serpentine.com>
Cc: Christian Axelsson <smiler@lanil.mine.nu>, linux-kernel@vger.kernel.org
Subject: Re: Centrino support
Date: Sun, 17 Aug 2003 01:32:50 +0300 [thread overview]
Message-ID: <200308170132.50312.insecure@mail.od.ua> (raw)
In-Reply-To: <1060982549.15347.30.camel@loke>
> > > Got a list of supported good working cards?
> >
> > There's a Dell TrueMobile card that uses the Orinoco chipset. If you're
> > feeling like life is too boring, there are cards based on the newer
> > Intersil dual 802.11b/g chipsets available, too, and though I haven't
> > checked into the shape of the drivers, I know they're under active
> > development.
>
> The Dell TrueMobile 1150 series are Agere/Orinoco/Hermes based (MiniPCI
> and PC-Card available). All other Dell TrueMobile cards are Broadcom
> based and have no Linux driver support either.
>
> There are also MiniPCI, PC-Card, USB adapters with 802.11a/b/g and Linux
> drivers available: http://sf.net/projects/madwifi
That driver contains a binary-only part.
<quote>
The ath_hal module contains the Atheros Hardware Access Layer (HAL).
This code manages much of the chip-specific operation of the 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".
</quote>
US was a free country. It gets worse by the day.
--
vda
next prev parent reply other threads:[~2003-08-16 22:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 18:13 Centrino support Jan Rychter
2003-08-15 18:29 ` Dave Jones
2003-08-15 18:33 ` Martin List-Petersen
2003-08-15 18:40 ` Bryan O'Sullivan
2003-08-15 20:24 ` Christian Axelsson
2003-08-15 20:35 ` Randy.Dunlap
2003-08-15 20:55 ` Bryan O'Sullivan
2003-08-15 21:22 ` Martin List-Petersen
2003-08-16 22:32 ` insecure [this message]
2003-08-17 4:16 ` Jamie Lokier
2003-08-15 20:35 ` Jan Rychter
2003-08-15 20:53 ` Bryan O'Sullivan
2003-08-16 19:58 ` Jan Rychter
2003-08-16 14:23 ` Dave Jones
2003-08-16 15:12 ` Alan Cox
2003-08-18 23:52 ` Rob Landley
2003-08-15 20:46 ` Brandon Stewart
2003-08-16 10:34 ` Stephan von Krawczynski
2003-08-16 19:58 ` Jan Rychter
2003-08-17 19:17 ` Jamie Lokier
2003-08-17 19:24 ` Alan Cox
2003-08-16 11:27 ` Tomas Szepe
2003-08-18 8:31 ` Helge Hafting
2003-08-19 21:15 ` James H. Cloos Jr.
2003-08-19 23:55 ` Jamie Lokier
2003-08-21 19:33 ` Micha Feigin
2003-08-17 20:07 ` Jussi Laako
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 20:32 Jean Tourrilhes
2003-08-15 22:36 Ricardo Galli
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=200308170132.50312.insecure@mail.od.ua \
--to=insecure@mail.od.ua \
--cc=bos@serpentine.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@list-petersen.se \
--cc=smiler@lanil.mine.nu \
/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