In message <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
