Date: Tue, 5 Jan 1999 09:00:10 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Doug Rabson <dfr@nlsystems.com> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, Warner Losh <imp@village.org>, Bill Paul <wpaul@skynet.ctr.columbia.edu>, current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo Message-ID: <Pine.LNX.4.04.9901050854510.21254-100000@feral-gw> In-Reply-To: <Pine.BSF.4.01.9901051017530.391-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.04.9901050854510.21254-100000>