Date: Sun, 04 Jul 1999 15:57:52 -0600 From: Warner Losh <imp@harmony.village.org> To: Doug Rabson <dfr@nlsystems.com> Cc: hackers@freebsd.org Subject: Re: The busspace modernization initiative. Message-ID: <199907042157.PAA44776@harmony.village.org> In-Reply-To: Your message of "Sun, 04 Jul 1999 22:40:05 BST." <Pine.BSF.4.10.9907042236480.54036-100000@salmon.nlsystems.com> References: <Pine.BSF.4.10.9907042236480.54036-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.10.9907042236480.54036-100000@salmon.nlsystems.com> Doug Rabson writes: : 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. This is true. However, that's just because that was what the code that I acquired from the newconfig people did. I don't think that it must be this way. : Do we really need to : support this api for common newconfig style drivers? Yes. I believe that we do. One thing that this is used for is to map things, even if they conflict. I'm sure I understand why it does that beyond checks for conflicts/valid I/O addresses in some drivers (mostly the scsi drivers). I'll have to look into what this API is supposed to do.... It is definitely heavily used (or at least used in almost all) in the few drivers that I've tried to port over.... It doesn't change the fact that bus_space_hanle_t is supposed to be an opaque type and many places in the three don't treat it as such.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907042157.PAA44776>