All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zappacky <zappacky.lists@gmail.com>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: Michael Buesch <mb@bu3sch.de>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: Add hooks for firmware debugging
Date: Sun, 18 May 2008 07:29:17 -0400	[thread overview]
Message-ID: <4830130D.6020401@gmail.com> (raw)
In-Reply-To: <69e28c910805171543u27a542b0nf2ab86e5702660e@mail.gmail.com>

Stefanik G=E1bor wrote:
>=20
> Another question: is this legal in the US? AFAIK this might conflict
> with FCC regulations. (Not sure about EU.)
>=20


Although I don't claim to be a lawyer, I found this information from=20
http://www.softwarefreedom.org/resources/2007/fcc-sdr-whitepaper.html,=20
which is a translation of the FCC's rules regarding software defined=20
radios (including 802.11 chips).

Snippet 1:

The rules require any manufacturer certifying a device under the new=20
process to take steps to prevent =93unauthorized=94 changes to the soft=
ware=20
on the device that might alter its radio frequency and power parameters=
=20
in a way that takes it out of compliance with the regulations known as=20
=46CC Part 15 regulations.2 The specific technology implemented to=20
accomplish this task is left to the manufacturers seeking certification=
,=20
although the FCC suggests several possible mechanisms that can serve as=
=20
such =93security measures.=943

Snippet 2:

Since software is a representation of a mathematical algorithm, it is=20
not a =93device=94, =93home electronic equipment=94 or a =93home electr=
onic ...=20
system.=9417 Further, there is no precedent for applying the device=20
certification rules to software except as installed as a component of a=
=20
specific hardware device. Indeed, the FCC has explicitly limited the=20
certification requirements to =93hardware-based device[s].=9418 Both of=
=20
these facts make it clear that the FCC rules do not apply to software b=
y=20
itself, but only to hardware-based devices.


What I get out of this, and out of poking in the legal babble, is that=20
as long as our firmware doesn't cause the hardware itself to violate FC=
C=20
specs, we're in the clear. According to Snippet 1, it shouldn't even be=
=20
possible to violate the specifications, but we all know how good=20
manufacturers are at stuff like that ;P.

-Andrew/Zappacky

(IANAL, Proceed at your own risk, etc)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-05-18 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 20:44 [PATCH] b43: Add hooks for firmware debugging Michael Buesch
2008-05-17 21:21 ` Stefanik Gábor
2008-05-17 21:24   ` Michael Buesch
2008-05-17 21:31     ` Rafał Miłecki
2008-05-17 22:27     ` Stefanik Gábor
2008-05-17 22:35       ` Michael Buesch
2008-05-17 22:43         ` Stefanik Gábor
2008-05-18 11:29           ` Zappacky [this message]
2008-05-17 23:33       ` Larry Finger

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=4830130D.6020401@gmail.com \
    --to=zappacky.lists@gmail.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=netrolller.3d@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.