From owner-freebsd-new-bus Wed Dec 29 1:47:13 1999 Delivered-To: freebsd-new-bus@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B05A814DAC for ; Wed, 29 Dec 1999 01:47:11 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id EAA13088; Wed, 29 Dec 1999 04:46:55 -0500 (EST) Date: Wed, 29 Dec 1999 04:46:55 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: new-bus@FreeBSD.ORG Subject: Re: Another question In-Reply-To: <199912290939.CAA01692@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Warner Losh wrote: > I've allocated a 16k chunk of system isa memory at the bridge level. > >From time to time children need a hunk of this memory to map in their > attribute memory. The attribute memory has various config registers > in it as well as the CIS. My thinking on the matter was that I'd > allocate the 16k chunk at bridge attach time, and then just give it > out to the children who are requesting a memory area be mapped in as > the default. However, when I go to do this, the allocation fails > because the bridge is holding the allocation. If I understand the issue correctly, your call to bus_alloc_resource() is failing because you are using bus_generic_alloc_resource() as PCCARD's BUS_ALLOC_RESOURCE() handler. What you should be doing is using your own method to arbitrate access to the parents already allocated resources (ie, not passing the resource allocation up to the parent's parent.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message