From owner-freebsd-acpi@FreeBSD.ORG  Thu Jun  3 13:36:07 2004
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8AF9216A4CE
	for <freebsd-acpi@freebsd.org>; Thu,  3 Jun 2004 13:36:07 -0700 (PDT)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2988A43D39
	for <freebsd-acpi@freebsd.org>; Thu,  3 Jun 2004 13:36:07 -0700 (PDT)
	(envelope-from nate@root.org)
Received: (qmail 44764 invoked by uid 1000); 3 Jun 2004 20:36:08 -0000
Date: Thu, 3 Jun 2004 13:36:08 -0700 (PDT)
From: Nate Lawson <nate@root.org>
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20040603.121143.08320551.imp@bsdimp.com>
Message-ID: <20040603133254.N44646@root.org>
References: <20040602160338.T38138@root.org>
	<200406030917.36901.jhb@FreeBSD.org>
	<20040603.121143.08320551.imp@bsdimp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-acpi@freebsd.org
Subject: Re: Patch: Defer bus_config_intr() until bus_alloc_resource()..
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2004 20:36:07 -0000

On Thu, 3 Jun 2004, M. Warner Losh wrote:
> In message: <20040603104616.I43856@root.org>
>             Nate Lawson <nate@root.org> writes:
> : With hotplug, we're going to need ways for a separate routine to set
> : resource attributes before bus_alloc_resource() time.  Plus, you yourself
> : are an advocate of a multi-pass probing approach that includes separating
> : resource reservation from allocation.
>
> I don't understand this comment at all.  We already support two
> different hot-plug technologies that allocate resources out of memory,
> i/o and irq space.  This is done by the bus that knows what resources
> the child needs before adding the child to the bus.

I don't have an example handy, but there are tables (SSDT) that can
appear/disappear with device insertion and it would be helpful to be able
to set up any resources described by them before device_attach() and alloc
time.  I'm interested why bus_{get,set}_resource even exist if our plan
all along was to defer all resource parsing to alloc time.

-Nate