> Here's the problem that I want to avoid. Imagine a case where a user has 2 > graphics cards. Say, an integrated i915 and a PCI R200. The installed > versions both use drm_core version N. Now the user wants to upgrade the R200 > driver, but the new R200 DRM requires drm_core version N+1. Suddenly the user > is forced to upgrade both drivers or neither driver.
I think we avoid this by having Kconfig do the hard part, and making sure all distribution vectors (snapshots, kernel, X distribs) install all kernel modules in an upgrade, so it forces the user to upgrade both drivers.. Kconfig can be used to stop building the DRM core into the kernel and building the DRM modules outside, so from a kernel release you have two choices, drm_core and all drivers i -kernel or everybody outside as modules, Now if you upgrade your DRM from snapshots or X release, the make install instructions for it install the new modules on top of the old ones and make sure that the drm_core goes in there as well.. I think kernel symbol versioning can help, but as its optional we can't rely on it .. I'm still not sold on the core/personality split myself I think it fixes ssome issues but opens up a lot more... and people are only seeing the first half clearly.. Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- 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
