From owner-freebsd-bugs@FreeBSD.ORG  Tue May 18 19:53:36 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id A6E9416A4CE; Tue, 18 May 2004 19:53:36 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8745643D31; Tue, 18 May 2004 19:53:36 -0700 (PDT)
	(envelope-from imp@FreeBSD.org)
Received: from freefall.freebsd.org (imp@localhost [127.0.0.1])
	i4J2ra6Y055557;	Tue, 18 May 2004 19:53:36 -0700 (PDT)
	(envelope-from imp@freefall.freebsd.org)
Received: (from imp@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4J2raw6055553;
	Tue, 18 May 2004 20:53:36 -0600 (MDT)
	(envelope-from imp)
Date: Tue, 18 May 2004 20:53:36 -0600 (MDT)
From: Warner Losh <imp@FreeBSD.org>
Message-Id: <200405190253.i4J2raw6055553@freefall.freebsd.org>
To: imp@FreeBSD.org, freebsd-bugs@FreeBSD.org, imp@FreeBSD.org
Subject: Re: kern/66848: cardbus power support breaks cardbus support on HP
	Omnibook XE2
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 May 2004 02:53:36 -0000

Synopsis: cardbus power support breaks cardbus support on HP Omnibook XE2

Responsible-Changed-From-To: freebsd-bugs->imp
Responsible-Changed-By: imp
Responsible-Changed-When: Tue May 18 20:52:41 MDT 2004
Responsible-Changed-Why: 
I'll fix it.

However, this isn't a power problem at all.  The real issue is that
the non acpi pcib driver doesn't restrict the memory ranges like it
should, causing the allocation of 0!

Warner


http://www.freebsd.org/cgi/query-pr.cgi?pr=66848