From owner-freebsd-stable@FreeBSD.ORG Sun Sep 14 14:14:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6162610656AD; Sun, 14 Sep 2008 14:14:47 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3DF898FC14; Sun, 14 Sep 2008 14:14:47 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id F06EB16112F; Sun, 14 Sep 2008 10:14:45 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 14 Sep 2008 10:14:45 -0400 X-Sasl-enc: Oi8GJI9bcBi/hF4t8zub+EbVDadPMcPsU+1c8Vj3YKaq 1221401685 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4D982634E; Sun, 14 Sep 2008 10:14:45 -0400 (EDT) Message-ID: <48CD1C54.7040208@incunabulum.net> Date: Sun, 14 Sep 2008 15:14:44 +0100 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.14 (X11/20080514) MIME-Version: 1.0 To: John Baldwin References: <48C8F684.8090409@incunabulum.net> <200809111043.18265.jhb@freebsd.org> <48CB21C7.9050706@incunabulum.net> <200809131109.06694.jhb@freebsd.org> In-Reply-To: <200809131109.06694.jhb@freebsd.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , FreeBSD stable Subject: Re: alpm(4) I/O range is claimed by ACPI X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2008 14:14:47 -0000 John Baldwin wrote: >> But surely if alpm(4) were to attach to such a range in this way, it >> would need to be a child of the acpi bus device, yes? >> > > No, the code in acpi_alloc_resources() does _not_ check for that. Any child > device with a specific allocation that falls in a system resource range will > succeed the allocation. > Ah, it is clearer after looking at devinfo output. Allocations will bubble up the bus drivers until they get to nexus. In this case, acpi is a child of nexus, therefore it will satisfy the allocation. >> It looks like there used to be a means of doing this in the FreeBSD >> driver but it got nuked. And that ASUS didn't much care about power >> management support in this machine... >> > > If you can re-enable it in such a way that it uses bus_alloc_resource(), then > the driver will probably work fine. > In that case it sounds like one needs to be able to use a hard-wired hint. It has been over a year since I've been able to do any proper work on mips , which needs a lot of this sort of thing, and I don't have a compelling case to do it now, so hopefully someone with an interest can pick this up. cheers BMS