From owner-freebsd-current@FreeBSD.ORG  Fri Jul 25 05:38:03 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 BE85237B401; Fri, 25 Jul 2003 05:38:03 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8746143F3F; Fri, 25 Jul 2003 05:38:01 -0700 (PDT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6PCbwFL073966;
	Fri, 25 Jul 2003 06:37:58 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Fri, 25 Jul 2003 06:36:55 -0600 (MDT)
Message-Id: <20030725.063655.88948403.imp@bsdimp.com>
To: adrian@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030725050226.GF41445@skywalker.creative.net.au>
References: <20030724231947.I30706@topperwein.pennasoft.com>
	<20030724.221744.66191711.imp@bsdimp.com>
	<20030725050226.GF41445@skywalker.creative.net.au>
X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 12:38:04 -0000

In message: <20030725050226.GF41445@skywalker.creative.net.au>
            Adrian Chadd <adrian@freebsd.org> writes:
: On Thu, Jul 24, 2003, M. Warner Losh wrote:
: > In message: <20030724231947.I30706@topperwein.pennasoft.com>
: >             Chris BeHanna <behanna@behanna.org> writes:
: > :     Can't they just redact that information from the spec.?
: > 
: > 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.
: 
: 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?
: 
: Can they now take "they took relevant steps" as a defence in a law court?

That's a very interesting question.

Warner