From owner-freebsd-current@FreeBSD.ORG Sat Sep 24 01:04:56 2005 Return-Path: X-Original-To: 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 1087816A41F for ; Sat, 24 Sep 2005 01:04:56 +0000 (GMT) (envelope-from arne@rfc2549.org) Received: from dagobah.rfc1149.org (dagobah.rfc1149.org [217.160.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86AD243D58 for ; Sat, 24 Sep 2005 01:04:54 +0000 (GMT) (envelope-from arne@rfc2549.org) Received: from dsl-213-023-197-006.arcor-ip.net ([213.23.197.6] helo=kamino.rfc1149.org) by dagobah.rfc1149.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.51 (FreeBSD)) id 1EIySx-0008B2-CH; Sat, 24 Sep 2005 03:04:41 +0200 Received: by kamino.rfc1149.org (Postfix, from userid 1001) id AFA4240B6; Sat, 24 Sep 2005 03:04:27 +0200 (CEST) From: Arne Schwabe To: "Brian K. White" In-Reply-To: <000a01c5c05d$fe286980$1f00000a@venti> (Brian K. White's message of "Fri, 23 Sep 2005 12:41:33 -0400") References: <433436E2.3040603@ThePacific.Net> <200509230725.21156.thierry@herbelot.com> <000a01c5c05d$fe286980$1f00000a@venti> Date: Sat, 24 Sep 2005 03:04:26 +0200 Message-ID: <86y85nnun9.fsf@kamino.rfc1149.org> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (i386--freebsd) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-RFC-Spam-Score: -2.3 (--) Cc: freebsd-current@freebsd.org, "Marcos Biscaysaqu - ThePacific.net" , thierry@herbelot.com Subject: Re: Linksys WRT54G with freebsd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 24 Sep 2005 01:04:56 -0000 "Brian K. White" writes: >> >> the last time I looked at it, there was also a problem with a binary-only >> driver, which is only available for Linux (therefore even a NetBSD >> port for >> WRT54G is not an option) > > Let me guess, the broadcom chip that has the ability to go into restricted > frequencies and so they are obligated by law to keep it's instructions > secret? Atheros chips can do that too iirc. At least you could trick an old hal into going to channel 17. Arne -- compiling millions of tiny c-programs...done checking for a working configure script... not found