From owner-freebsd-mobile@FreeBSD.ORG  Mon Sep 27 10:37:41 2004
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CB72816A4CE
	for <freebsd-mobile@freebsd.org>;
	Mon, 27 Sep 2004 10:37:41 +0000 (GMT)
Received: from gw.pelleg.org (gw.pelleg.org [205.201.13.235])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7269D43D53
	for <freebsd-mobile@freebsd.org>;
	Mon, 27 Sep 2004 10:37:41 +0000 (GMT)
	(envelope-from daniel@pelleg.org)
Received: from lank.here (lank.wburn [192.168.3.41])
	by gw.pelleg.org (Postfix) with ESMTP id CE2385A53
	for <freebsd-mobile@freebsd.org>;
	Mon, 27 Sep 2004 06:37:39 -0400 (EDT)
Received: by lank.here (Postfix, from userid 7675)
	id B72D043B5; Mon, 27 Sep 2004 06:37:37 -0400 (EDT)
To: freebsd-mobile@freebsd.org
References: <u2s4qltqais.fsf@lark.auton.cs.cmu.edu>
From: Dan Pelleg <daniel+bsd@pelleg.org>
Date: Mon, 27 Sep 2004 06:37:37 -0400
In-Reply-To: <414C16F9.3000608@nagilum.org> (Nagilum's message of "Sat, 18
 Sep 2004 13:07:37 +0200")
Message-ID: <u2sy8iw0zgu.fsf_-_@lank.wburn>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Security Through
 Obscurity, berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: wi driver problems: WEP+ACPI, -5.3B5
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Sep 2004 10:37:41 -0000


Just wanted to document that the problem I reported goes away with
hw.pci.allow_unsupported_io_range="1"

-- 

  Dan Pelleg