All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuffed Crust <pizza@shaftnet.org>
To: bas.mevissen@hetnet.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Broadcom BCM4306/BCM2050  support
Date: Tue, 29 Apr 2003 10:40:55 -0400	[thread overview]
Message-ID: <20030429144055.GA11583@shaftnet.org> (raw)
In-Reply-To: <4b4e01c30e4e$0352c5a0$d16897c2@hetnet.nl>

[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]

On Tue, Apr 29, 2003 at 02:51:12PM +0200, bas.mevissen@hetnet.nl 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 linux-wlan-ng project only handles the prism2/2.5/3 chipsets, which 
are *extremely* well documented (and 2.4G-only), so there really isn't 
anything to "handle"; from the driver perspective  you just say "give 
me channel X" and that's it.   If the eeprom-based tables say you can 
use the channel, it lets you; otherwise it's No Soup For You.  

Intersil is a poor example; they've generally been quite forthcoming
with documentation.  Granted, the docs for the PrismGT/etc stuff are
pretty bad, but you can get them without selling your soul. 

(it's also worth mentioning that Intersil partially funded
linux-wlan-ng's development)
 
RF tables and regulation might be an excuse chipset companies use to
hide their specs, but the real reasons tend to be a bit more along the
lines of:

"We want to protect our valuable IP"

...which translates to:

"We want to protect our violations of other people's valuable IP"

It's CYA, plain and simple.  They're so terrified of litigation that 
they feel that *any* semi-public information (even if only source code) 
is a threat. 

Many of them genuinely want to provide Linux support, in the form of
binary drivers much like Windows has.  Then they balk when realizing
what a support hell (and $$$) it will be to pull it off without
providing source code, thanks to the monolothic nature of the Linux
kernel. 

Or at least that's been my experience in the past year.

 - Pizza
-- 
Solomon Peachy                                   pizza@f*cktheusers.org
                                                           ICQ #1318444
Quidquid latine dictum sit, altum viditur                 Melbourne, FL

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2003-04-29 14:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 12:51 Broadcom BCM4306/BCM2050 support bas.mevissen
2003-04-29 14:40 ` Stuffed Crust [this message]
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=20030429144055.GA11583@shaftnet.org \
    --to=pizza@shaftnet.org \
    --cc=bas.mevissen@hetnet.nl \
    --cc=linux-kernel@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 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.