On Sat, Sep 04, 2004 at 01:12:16AM +0100, Dave Airlie wrote: > DRM core - just the stub registration procedure and handling any > shared resources like the device major number, and perhaps parts of sysfs > and class code. This interface gets set in stone as quickly as possible > and is as minimal as can be, (Jon Smirls dyn-minor patch will help a fair > bit also). All the core does is allow DRMs to register and de-register in > a nice easy fashion and not interfere with each other. This drmcore.o can > either be linked into the kernel (ala the fb core) or a module, but in > theory it should only really be shipped with the kernel - (for compat > reasons the DRM tree will ship it for older systems).
Ok. > DRM library - this contains all the non-card specific code, AGP > interface, buffers interface, memory allocation, context handling etc. > This is mostly stuff that is in templated header files now moved into C > files along the lines of what I've done in the drmlib-0-0-1-branch. This > file gets linked into each drm module, if you build two drivers into the > kernel it gets shared automatically as far as I can see, if you build as > modules they both end up with the code, for the DRM the single card is the > primary case so I don't mind losing some resources for having different > cards in a machine. Ok except you should build this only once. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel