From owner-freebsd-new-bus Wed Dec 29 1:50:25 1999 Delivered-To: freebsd-new-bus@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2E1CE14E46 for ; Wed, 29 Dec 1999 01:50:23 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA43006; Wed, 29 Dec 1999 02:50:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA01762; Wed, 29 Dec 1999 02:50:21 -0700 (MST) Message-Id: <199912290950.CAA01762@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: Another question Cc: new-bus@FreeBSD.ORG In-reply-to: Your message of "Wed, 29 Dec 1999 04:46:55 EST." References: Date: Wed, 29 Dec 1999 02:50:21 -0700 From: Warner Losh Sender: owner-freebsd-new-bus@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : 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.) Ahhhh. The light bulb grows bright where once it was dim. That makes perfect sense. For some things I pass it up, for others I give from the space that I have. I'll have to go look at the nexus code to see what it does... Thanks for the pointer. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-new-bus" in the body of the message