From owner-freebsd-hackers Sun Jul 4 14:40:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2806614BFF for ; Sun, 4 Jul 1999 14:40:15 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id WAA66694; Sun, 4 Jul 1999 22:40:05 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 4 Jul 1999 22:40:05 +0100 (BST) From: Doug Rabson To: Warner Losh Cc: hackers@freebsd.org Subject: Re: The busspace modernization initiative. In-Reply-To: <199907042003.OAA43735@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 4 Jul 1999, Warner Losh wrote: > In message Doug Rabson writes: > : I think you are on the right lines here. Where does the resource come > : from? Are you going to support bus_space_map() and if so, how are you > : planning to call BUS_ALLOC_RESOURCE? > > In i386/i386/resource.c :-). Here's what is there now. It looks like > it currently bypasses BUS_ALLOC_RESOURCE, going to the resource > manager (rman) directly. Do you have any comments on this code? Or > would you rather I send you a complete patch/diff to comment on? This seems to bypass the nexus completely which isn't right. It wouldn't detect conflicts between bus_space_alloc and the new-bus resource apis since it has its own instances of struct rman. Do we really need to support this api for common newconfig style drivers? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message