Thanks for the explanation. But I think I came up with a simpler way of getting permanent maps. Savage3D has a limited video mem size of 16MB, on Savage4 the limit is 32MB. So I could just make permanent maps with the respective maximum sizes and fix the DDX driver to expect maps with these sizes, regardless of the real amount of video memory.
Another option would be to not map the real framebuffer at all. I believe it's not needed by the 3D driver. All it needs is the aperture which has a fixed size and location. Again, I would have to fix the DDX driver to not try to create a map of the real framebuffer. Either way, I'll avoid touching the hardware during DRM initialization. I believe hardware initialization would be the business of a FB driver (when someone gets to writing one). (Also see my comment about Mesa-solo below ...) I'm also going to make a permanent map of MMIO registers for now, but I'm going to get rid of it eventually. When the DRM is finished I believe the 3D driver will never need to touch MMIO registers directly. This is also desirable from a security POV. Felix On Thu, 16 Sep 2004 21:19:30 -0400 Jon Smirl <[EMAIL PROTECTED]> wrote: > The plan here is to slowly get X out of the hardware initialization > business. Anything that is playing with registers from user space > needs to be migrated into the drivers. Another factor is the desire to > slowly get X into a position where it doesn't need to run as root. As > long as X plays with the registers from user space it has to stay a > root priv app. > > X on GL runs on top of mesa-solo. Since X on GL doesn't use the 2D > DDXs the hardware initialization has to come from somewhere else. > Things needing root priv need to go into the driver. But there is > nothing stopping you from computing register values in user space and > then passing them into a small IOCTL. The user space code for the > IOCTL is in mesa-solo. The goal is to end up with a controlling X app > running non-root which then authorizes non-root clients. > > While we are in transition initialization code needs to go into the > DDX and mesa-solo driver/server directories. It going to take a while > to convert everything over. The process will probably be different for > each card. There is no kernel FB driver for savage right now. Until someone writes one Mesa-solo won't work on savages, right? > > On Fri, 17 Sep 2004 00:20:04 +0200, Felix Kühling <[EMAIL PROTECTED]> wrote: [snip] | Felix Kühling <[EMAIL PROTECTED]> http://fxk.de.vu | | PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
