From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: "David S. Miller" <davem@redhat.com>
Cc: Martin List-Petersen <martin@list-petersen.dk>,
bas.mevissen@hetnet.nl, linux-kernel@vger.kernel.org
Subject: Re: Broadcom BCM4306/BCM2050 support
Date: Tue, 29 Apr 2003 13:38:50 +0200 [thread overview]
Message-ID: <3EAE644A.2000101@gmx.net> (raw)
In-Reply-To: <1051614381.21135.5.camel@rth.ninka.net>
David S. Miller wrote:
> On Mon, 2003-04-28 at 23:16, Martin List-Petersen wrote:
>
>>>I couldn't find any Linux support for these WLAN chips with
>>>google or on this lists archives. So I would like to ask it here:
>>
>>It seems, that the specs haven't been released yet. There are quite a few Wlan
>>cards out there based on the Broadcom chips (nearly all cards, that support
>>802.11g), so it's quite a shame. (Actually this fits the the TrueMobile 1180,
>>1300 and 1400, speaking of Dell wireless lan cards).
>
> ...
>
>>The same problem is with the Intel Prowireless 2100 (Centrino) WLan card. No
>>Linux support available yet, which is another choice for the Dell notebooks at
>>the moment.
>
>
> Don't expect specs or opensource drivers for any of these pieces
> of hardware until these vendors figure out a way to hide the frequency
> programming interface.
>
> Ie. these cards can be programmed to transmit at any frequency,
> and various government agencies don't like it when f.e. users can
> transmit on military frequencies and stuff like that.
Cool.
> The only halfway plausible idea I've seen is to not document the
> frequency programming registers, and users get a "region" key file that
> has opaque register values to program into the appropriate registers.
> The file is per-region (one for US, Germany, etc.)and the wireless
> kernel driver reads in this file to do the frequency programming.
>
> So don't blame the vendors on this one, several of them would love
> to publish drivers public for their cards, but simply cannot with
> upsetting federal regulators.
/me wants binary only driver for these cards to build opensource driver
with ability to set "interesting" frequency range.
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2003-04-29 11:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 6:16 Broadcom BCM4306/BCM2050 support Martin List-Petersen
2003-04-29 11:06 ` David S. Miller
2003-04-29 11:38 ` Carl-Daniel Hailfinger [this message]
2003-04-29 12:12 ` Martin List-Petersen
2003-04-29 12:27 ` Grzegorz Jaskiewicz
2003-04-29 13:26 ` Richard B. Johnson
2003-04-29 13:18 ` Alan Cox
2003-04-29 14:45 ` Stuffed Crust
2003-04-29 13:48 ` Carl-Daniel Hailfinger
2003-04-29 13:28 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 13:35 Martin List-Petersen
2003-05-01 13:22 bas.mevissen
2003-04-29 16:58 harry
2003-04-29 21:19 ` Oliver Neukum
2003-04-29 15:22 Nicholas Berry
2003-04-29 12:51 bas.mevissen
2003-04-29 14:40 ` Stuffed Crust
2003-05-01 11:01 ` David S. Miller
2003-04-29 12:28 bas.mevissen
2003-04-29 12:58 ` Martin List-Petersen
2003-04-28 15:53 bas.mevissen
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=3EAE644A.2000101@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=bas.mevissen@hetnet.nl \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@list-petersen.dk \
/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).