From owner-freebsd-current@FreeBSD.ORG Fri Jul 25 10:17:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 455BC37B401; Fri, 25 Jul 2003 10:17:44 -0700 (PDT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3158443F85; Fri, 25 Jul 2003 10:17:43 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.9/8.12.3) with ESMTP id h6PHHJuD027654; Fri, 25 Jul 2003 10:17:19 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.9/8.12.3/Submit) id h6PHHIoq027653; Fri, 25 Jul 2003 10:17:18 -0700 Date: Fri, 25 Jul 2003 10:17:18 -0700 From: Brooks Davis To: "M. Warner Losh" Message-ID: <20030725171718.GB23178@Odin.AC.HMC.Edu> References: <20030724231947.I30706@topperwein.pennasoft.com> <20030724.221744.66191711.imp@bsdimp.com> <20030725050226.GF41445@skywalker.creative.net.au> <20030725.063655.88948403.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oLBj+sq0vYjzfsbl" Content-Disposition: inline In-Reply-To: <20030725.063655.88948403.imp@bsdimp.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-milter (http://amavis.org/) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org Subject: Re: We have ath, now what about Broadcom? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 17:17:44 -0000 --oLBj+sq0vYjzfsbl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 25, 2003 at 06:36:55AM -0600, M. Warner Losh wrote: > In message: <20030725050226.GF41445@skywalker.creative.net.au> > Adrian Chadd writes: > : On Thu, Jul 24, 2003, M. Warner Losh wrote: > : > In message: <20030724231947.I30706@topperwein.pennasoft.com> > : > Chris BeHanna writes: > : > : Can't they just redact that information from the spec.? > : >=20 > : > Typically no. Even in a redacted spec it would be painfully obvious > : > what to do. Also, different regulatory domains have different > : > frequencies that are real no-nos in other regulatory domains and > : > they'd need to document how to properly generate the RF in both > : > cases. > :=20 > : So, assuming that there's at least one person smart enough to reverse > : engineer the binary driver but stupid enough to release it publicly, > : what happens to the manufacturer there? > :=20 > : Can they now take "they took relevant steps" as a defence in a law cour= t? >=20 > That's a very interesting question. I would guess that if there were wide-spread problems, they might cancel the license for the devices until they deliberatly broke the firmware interfaces, but it's probably the case that they aren't going to hold the manufacture responsible for blatent, high-effort misuse of the product even if they technical could. On the other hand these modern, programmable radios are probably more of an issue then the current problems with illegal amplification or overly high-gain antennas. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --oLBj+sq0vYjzfsbl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/IWYdXY6L6fI4GtQRApSwAKCB2yd/zjKIinCS+TPDYq4DrCIztgCg4EuN mMROUCLHotfRcq9+lD3QVso= =sLcZ -----END PGP SIGNATURE----- --oLBj+sq0vYjzfsbl--