mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Martin List-Petersen <martin@list-petersen.dk>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
	"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 09:26:32 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304290851030.23672@chaos> (raw)
In-Reply-To: <1051618337.3eae6c218bd3c@roadrunner.hulpsystems.net>

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
federal law prohibiting the disclosure of a radio message by a
third party. This means that the media, or even law enforcement
can't listen to a private radio (cell phone) conversation and
then disclose its content. At one time, cell phones used FM
at 960 MHz. This could be readily received by receivers designed
for Amateur Radio use. For a time, the FCC refused to Type Approve
receivers that cover these frequencies. However, most Hams know
how to fix their receivers so they can receive whatever they want
and Type Approval was only required for receivers that were designed
to be sold. You could build anything you want for yourself. This
refusal to Type Approve receivers was a trick to make the usual
receiver owner think that there was some dumb regulation when,
in fact, under the Communications Act of 1934 (as amended), there
can't be such a regulation without creating a new public law, which
hasn't happened and probably will not.

Recently, some broadcast satellite companies have tried to
get the FCC to declare that their transmissions are private
and unauthorized reception should be unlawful. The FCC has
continually postponed any such declaration because, if once
broadcast, a radio signal doesn't become public, then anybody
could sue every radio transmitter operator to prevent the
trespass of "their" signals onto private property.
You can't have it both ways, either radio signals are public
and, therefore cannot commit a trespass, or they are private
and can.

But, unlike some other countries regulators, the FCC has
steadfastly refused to allow broadcasters, even satellite
broadcasters, to pursue such extortion. Basically, once
a signal leaves an antenna, it becomes public property.

The same is not true for cable and "guided waves". Satellite
broadcasters have not been able to convince the FCC that
their transmissions are "guided waves". However, some private
RF link companies signals, including some that use satellites,
are considered "guided waves" and cannot be used without
permission.

Various commercial interests have convinced governments of
many other countries that they "own" their radio signals and
therefore different regulations exist in many other countries.
In the UK, for instance, one has to purchase a license to
use a receiver (you know, some Sony Walkman). This is, in my
opinion, extremely repressive. It would be nice for somebody
to start suing the BBC (and others) to recover damages for
the criminal trespass of "their" radio signals onto private
property. After a few such lawsuits, the ownership of such
broadcast signals would revert to the public, just like in
the US.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.


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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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=Pine.LNX.4.53.0304290851030.23672@chaos \
    --to=root@chaos.analogic.com \
    --cc=bas.mevissen@hetnet.nl \
    --cc=c-d.hailfinger.kernel.2003@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®