linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: root@chaos.analogic.com
Cc: Martin List-Petersen <martin@list-petersen.dk>,
	"David S. Miller" <davem@redhat.com>,
	bas.mevissen@hetnet.nl, linux-kernel@vger.kernel.org
Subject: Re: Broadcom BCM4306/BCM2050  support
Date: Tue, 29 Apr 2003 15:48:06 +0200	[thread overview]
Message-ID: <3EAE8296.9010904@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0304290851030.23672@chaos>

Richard B. Johnson wrote:
> On Tue, 29 Apr 2003, 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.
>>>
>>>/me wants binary only driver for these cards to build opensource driver
>>>with ability to set "interesting" frequency range.
>>>
>>
>>It's there for Windows :) So ...
> 
> 
> Contrary to popular opinion, there is no FCC regulation prohibiting
> one from receiving some particular frequency. There is, however, a

Contrary to popular opinion, not everybody lives in the US.
Here in Germany, receiving some particular frequencies (e.g. those used
by the police) was prohibited a few years ago (I don't know exactly if
they changed the law). The argument was that some receiver types emitted
a weak signal on the frequency they were listening to (and could be
tuned to become a private radio station) which could interfere with the
low-power police devices. However, it was simply not sensible to
prohibit all radios, so they were constained to a specific frequency range.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


  parent reply	other threads:[~2003-04-29 13:35 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
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 [this message]
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=3EAE8296.9010904@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 \
    --cc=root@chaos.analogic.com \
    /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).