From owner-freebsd-current Tue Jan 5 09:02:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06813 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:02:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06803 for ; Tue, 5 Jan 1999 09:02:46 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id JAA21280; Tue, 5 Jan 1999 09:00:11 -0800 Date: Tue, 5 Jan 1999 09:00:10 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Doug Rabson cc: Garrett Wollman , Warner Losh , Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > How do you view this integration? I'm confused... What needs to be > > > integrated? > > > > When you activate a memory or I/O resource, the appropriate magic > > should happen such that included in the stuff you get back is > > something which can be used to access that resource quickly. Stuff > > like bus_space_alloc should be handled by the bus driver in > > coordination with the resource manager. (It should be implemented as > > a method call on the device's parent, so that it has all the necessary > > context pre-computed.) > > I think that this is the right approach. The interface for PCI busses > should have methods to manage the various device resources and these will > be able to provide bus_space handles as necessary. The resources should > not need to be mapped directly by the pci driver. I'm currently > prototyping the new PCI interface (or I will be as soon as I can get that > wretched sysinstall program working properly on the alpha) and I'll add > something like this. > Sounds like the Solaris DKI/DDI. Will you be making the bus_space handles hierarchical and bidirectional? That is, you can do bus_space_XXX for a CPU's access to i/o or memory space on a PCI device, but can you also see about a PCI device's view of memory (or another PCI device) such that dma handles are managed similarily? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message