All of lore.kernel.org
 help / color / mirror / Atom feed
From: <bas.mevissen@hetnet.nl>
To: "Martin List-Petersen" <martin@list-petersen.dk>,
	"David S. Miller" <davem@redhat.com>
Cc: <bas.mevissen@hetnet.nl>, <linux-kernel@vger.kernel.org>
Subject: RE: Broadcom BCM4306/BCM2050  support
Date: Tue, 29 Apr 2003 14:51:12 +0200	[thread overview]
Message-ID: <4b4e01c30e4e$0352c5a0$d16897c2@hetnet.nl> (raw)


David S. Miller wrote:

> 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.

What did Intersil do? How did the linux-wlan-ng project handle this?

> 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.

Here in The Netherlands, it is quite common to use a US version of Windows and to keep (most of)  the regional settings of the US. So on Windows, most of the time the region is likely to be wrong. I gues that in cases where things are critical, a different firmware version is used. 

It is not really a practical problem however, because the allowed frequencies have become pretty the same over time. The same applies to modems: they are also country-specific. But in practice, it is not really a concern.

But how to go furter with this? Does someone have contacts within Broadcom?

Regards,

Bas.



--------------------------------------------------------------------------------

             reply	other threads:[~2003-04-29 12:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 12:51 bas.mevissen [this message]
2003-04-29 14:40 ` Broadcom BCM4306/BCM2050 support Stuffed Crust
2003-05-01 11:01   ` David S. Miller
  -- 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:28 bas.mevissen
2003-04-29 12:58 ` Martin List-Petersen
2003-04-29  6:16 Martin List-Petersen
2003-04-29 11:06 ` David S. Miller
2003-04-29 11:38   ` Carl-Daniel Hailfinger
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
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='4b4e01c30e4e$0352c5a0$d16897c2@hetnet.nl' \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.