From: Andrew McGregor <andrew@indranet.co.nz>
To: root@chaos.analogic.com
Cc: Guennadi Liakhovetski <gl@dsa-ac.de>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
linux-kernel@vger.kernel.org
Subject: Re: [somewhat OT] binary modules agaaaain
Date: Sat, 24 Apr 2004 14:29:25 +1200 [thread overview]
Message-ID: <59185674.1082816965@[192.168.1.249]> (raw)
In-Reply-To: <Pine.LNX.4.53.0404230812190.2732@chaos>
--On Friday, 23 April 2004 8:29 a.m. -0400 "Richard B. Johnson"
<root@chaos.analogic.com> wrote:
> On Fri, 23 Apr 2004, Andrew McGregor wrote:
>
>> And it must, if only because there are laws that require some device
>> drivers to be binary only.
>
>
> WRONG. I work in the industry. There are no such rule(s). In fact,
> it's quite the opposite. Anything that is FCC Type Accepted or
> Type Approved has, as a matter of law, its complete design
> information, to the extent required for FCC Type Acceptance,
> available for public inspection in the Public Reference Room.
> Therefore, it can't be hidden as something "proprietary".
I was aware of that much, but does that actually include the code of the
drivers?
By the way, there are examples outside wireless as well, but they are very
exotic.
>> I kid you not, take a look at the FCC software radio rules. Some
>> wireless cards fall into their definition.
>>
>
> The requirement that the devices "not be modified" has been interpreted
> by some to mean that software can't be supplied to the end-user. This
> is an interpretation and, in fact, an invalid one.
That is very good news. I'll have to get an opinion myself, of course, but
I think it is good to get this clarified in public.
> If a user were to modify the device, (presumably by changing the
> software) it is no longer Type Approved in the case of receivers,
> and, if a transmitter the modification must be done in accordance
> with "good standards of engineering practice" under the authority
> of a holder of a General Radiotelephone (or Radiotelegraph) License.
>
> The operation of a receiver that is not "Type Approved" is not
> unlawful unless it produces "harmful interference". Type Approval
> was necessary to SELL a device that generates radio frequency
> energy, not to use it.
>
> FYI Amateur Radio Operators make receivers and transmitters. They
> are not Type Approved. Holders of FCC Radiotelephone licenses are
> allowed to make or modify even 50,000 watt broadcast transmitters.
I was aware of the situation regarding license holders.
>
> Cheers,
> Dick Johnson
Thanks for pointing this out,
Andrew
---------
Andrew McGregor
Director, Scientific Advisor
IndraNet Technologies Ltd
http://www.indranet-technologies.com/
next prev parent reply other threads:[~2004-04-24 2:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 15:53 Guennadi Liakhovetski
2004-04-20 8:39 ` Geert Uytterhoeven
2004-04-20 10:23 ` Guennadi Liakhovetski
2004-04-20 14:11 ` Bartlomiej Zolnierkiewicz
2004-04-20 15:08 ` Guennadi Liakhovetski
2004-04-21 2:24 ` Horst von Brand
2004-04-22 14:13 ` Grzegorz Kulewski
2004-04-23 11:28 ` Andrew McGregor
2004-04-23 12:29 ` Richard B. Johnson
2004-04-24 2:29 ` Andrew McGregor [this message]
2004-04-22 16:19 ` Charles Shannon Hendrix
2004-04-22 18:55 ` Bartlomiej Zolnierkiewicz
[not found] <1MJlZ-4mT-47@gated-at.bofh.it>
2004-04-24 10:03 ` Ihar 'Philips' Filipau
2004-04-24 20:00 ` Guennadi Liakhovetski
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='59185674.1082816965@[192.168.1.249]' \
--to=andrew@indranet.co.nz \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=gl@dsa-ac.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®