Matthew Jacob wrote: > > Thanks for the clarification. I was confusing BUS_SPACE_MAXSIZE > > with BUS_SPACE_MAXSIZE_24BIT and BUS_SPACE_MAXSIZE_32BIT. > > > > It's probably too late to rename BUS_SPACE_MAXSIZE to something > > like BUS_SPACE_MAXXFER. 8-(. > > Yes. If we've understood it at all. There are no documents really describing > it.
I was going to mention this, but I censured myself so that it wouldn't look like I was whinging... 8-) 8-). The documentation in these areas is atrocious. There needs to be a documentation requirement for the commit of huge things, like bus space, CAM, devfs, GEOM, etc. ... > > > BUS_SPACE_MAXSIZE seems to be related to the 'largest xfer you > > > will be allowed to do at one time'- which is wrong because MAXPHYS > > > is larger. > > > > Yeah, I get that now. No need to beat me up, I can take care > > of it myself. 8-) 8-). > > No, no.... at least you showed some interest :-) If that's supposed to trick me into doing the missing documentation, it's not working... 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
