From: "David S. Miller" <davem@redhat.com>
To: Stuffed Crust <pizza@shaftnet.org>
Cc: bas.mevissen@hetnet.nl, linux-kernel@vger.kernel.org
Subject: Re: Broadcom BCM4306/BCM2050 support
Date: 01 May 2003 04:01:28 -0700 [thread overview]
Message-ID: <1051786888.8772.7.camel@rth.ninka.net> (raw)
In-Reply-To: <20030429144055.GA11583@shaftnet.org>
On Tue, 2003-04-29 at 07:40, Stuffed Crust wrote:
> 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.
This is very far from the truth. And as Alan and myself have been
talking to upper management entities at various wireless card
companies we know the real reason has to do with making regulation
agencies happy. They do have drivers, and they do want to publish
them and yes they recognize that this will expose a lot of their
IP and they accept that.
--
David S. Miller <davem@redhat.com>
next prev parent reply other threads:[~2003-05-01 23:51 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
2003-05-01 11:01 ` David S. Miller [this message]
-- 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=1051786888.8772.7.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=bas.mevissen@hetnet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=pizza@shaftnet.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 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).