From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Martin List-Petersen <martin@list-petersen.dk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Broadcom BCM4306/BCM2050 support
Date: 29 Apr 2003 13:27:49 +0100 [thread overview]
Message-ID: <1051619268.21965.20.camel@gregs> (raw)
In-Reply-To: <1051618337.3eae6c218bd3c@roadrunner.hulpsystems.net>
On Tue, 2003-04-29 at 13:12, Martin List-Petersen wrote:
> Citat Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>:
>
> > > 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.
Well, there are guys that are able to change this frequency without open
documentation - so it is just not good argument.
I will rather say that this is misdesign - allowing to do more than is
allowed....
--
Grzegorz Jaskiewicz <gj@pointblue.com.pl>
K4 Labs
next prev parent reply other threads:[~2003-04-29 12:15 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
2003-04-29 12:12 ` Martin List-Petersen
2003-04-29 12:27 ` Grzegorz Jaskiewicz [this message]
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=1051619268.21965.20.camel@gregs \
--to=gj@pointblue.com.pl \
--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