what to do with vtophys()

outside of work, I do some things with OpenBSD. Over the last month or so, I’ve been poking at the DRI code, mostly to make it compile on my laptop. Why is it taking so long? I don’t know C, and are learning on the fly. Kernel space makes it interesting.

One problem with compiling: the code uses ‘vtophys()’, which is not portable. My laptop is running in AMD64 mode, which doesn’t have vtophys(). The solution: ‘bus_space_vaddr()’. it essentially is a drop-in replacement for vtophys(), but I have to set up the bus_space area first. Thats proving to be a little more of a challenge than I hoped. I think I’ll have to edit the headers, and add (yuck) some entries into a struct, so I can pass around the appropriate information.