From owner-freebsd-current Thu Dec 31 12:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17366 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:46:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17361 for ; Thu, 31 Dec 1998 12:46:22 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zvoyg-0000Vh-00; Thu, 31 Dec 1998 13:45:54 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id NAA01055; Thu, 31 Dec 1998 13:43:50 -0700 (MST) Message-Id: <199812312043.NAA01055@harmony.village.org> To: Garrett Wollman Subject: Re: bus_space_foo and bus_dmamap_foo Cc: Bill Paul , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 31 Dec 1998 15:33:11 EST." <199812312033.PAA06966@khavrinen.lcs.mit.edu> References: <199812312033.PAA06966@khavrinen.lcs.mit.edu> <199812311858.NAA05191@skynet.ctr.columbia.edu> <199812311928.MAA00612@harmony.village.org> Date: Thu, 31 Dec 1998 13:43:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812312033.PAA06966@khavrinen.lcs.mit.edu> Garrett Wollman writes: : < said: : : > True. Likely the NetBSD interface should be adopted, unless there is : > a compelling reason not to do this. : : A significant problem with all of this stuff is that it pre-dates : DFR's bus code. This is a problem because it recapitulates the bus : hierarchy which new-bus is there to construct for us. It was my understanding from talking to Justin that these areas were basically orthoginal. busspace and busdma are used to talk to the hardware, while DFR's new bus stuff is more a configuration thing rather than talking to the actual hardware. : What would be preferable would be for this mechanism to be integrated : with new-bus and the resource manager, so that when a driver requests : a resource, it automatically gets any other context necessary to : access that resource. The resource manager already has some hooks, in : particular the r_vaddr member in struct resource, for that purpose, as : well as the entire distinction between allocating and activating a : resource. How do you view this integration? I'm confused... What needs to be integrated? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message