> > The video driver's properties seem to be intended for use by the UI > > and not by other parts of xine-lib. Are we not overloading their > > intended use? > > According to me, it won't worth nothing. > However I will discuss it on the xine mailing-list.
OK thanks. > > I'll still need a way to get at the video memory offsets for the > > surfaces in order to pass them to the hardware decoder. I don't think > > I can work them out from the virtual addresses without knowing the > > base address of DirectFB's mapped memory. Any suggestions? > > Well, libcle266mpegdec already accesses /dev/fbX to mmap the mmio, > thus you could mmap framebuffer memory to get the base address. That's true but when the library maps /dev/fbX itself, it'll get a different virtual address for the framebuffer memory than DirectFB will (it's a separate file open and mmap call and, as far as I know, there is no connection between multiple mappings to the same file or device; a quick check of /proc/NNNN/maps seems to confirm this). If I could get to the physical addresses, I could get the offsets via the framebuffer device's physical base address. However, I don't know of any user space API to do virtual to physical address mappings. Regards, Mark _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
