From: Thomas <uni...@sh...> - 2005-06-29 09:18:31
|
Hi! > On 6/28/05, Ian Romanick <id...@us...> wrote: >> > 3) Can the driver pre-build the AGP/PCI gart maps? If these maps are >> > marked differently it is way for my driver to tell AGP from PCI card= s. >> >> I would advise against that. There are (rare) cases where user-mode >> wants to select AGP parameters, AGP mode vs. PCI mode, etc. If AGP is >> acquired and those maps added at module load, the only way to make tho= se >> selections will be via module paramters. Yuck. > > Currently the drivers are AddMap'ing multiple little maps over the AGP > area, but the area is basically split into two area: private for the > master and public for the DRI clients to write to. > > So to get around the root priv requirement of AddMap I could have DRM > initially create a map which only allows master access to AGP space. > Then the non-root master could safely AddMap sub-maps which must exist > inside of the predefined AGP map. These sub-maps would lower the priv > requirements for parts of AGP space and allow the clients to run. > The via drm module needs a kernel 2MB _RESTRICTED AGP map for the command stream. The master must not have access to that part, since it will allow a non-root master to modify the command stream once it has been security-checked. How will drmAgpAlloc be handled? I mean, how will DRM know how big the initial map will be? /Thomas > -- > Jon Smirl > jon...@gm... > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dclick > -- > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel > |