Ian Romanick wrote:
So, you have x_ata.ko and y_ata.ko that are both linked with libata. What happens when when the user loads both modules at once? How do you avoid symbol conflicts from the libata linked to both drivers? This is basically what the DRM does, but we have the evil macros (no, I don't like them either) to prevent the symbol conflicts.


libata is a library module.

Just like userspace libraries, libata module is loaded once, then shared among N drivers that reference its symbols. The first module loaded will cause libata to be loaded. The second module loaded will simply reference the already-loaded libata.

There is no need for additional work to prevent symbol conflicts.

        Jeff




------------------------------------------------------- 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

Reply via email to