Jon Smirl wrote:
The only case I see a problem is when drm-core is compiled into the
kernel. Why don't we just change the Makefile to default to copying the
CVS code into the kernel source tree and tell the user to rebuild his
kernel?
I don't think that will fly with Joe-user that just wants to upgrade his graphics driver. The other problem case is if the user has two graphics cards in his system. He wants to upgrade the driver for one of them (or install a new driver for a new card), but the interface between the device-independent (in-kernel) layer and the device-dependent (in-kernel) layer has changed.
Unless there is some way to have multiple device-independent modules (on a built-in and a module) loaded, the user is stuck in a situation where he has to update both drivers, but it may not be obvious that they need to do so.
I don't think this situation is likely to happen, but if there is even the potential for it to happen, we will get bitten. :(
Then for us DRM hackers just have another make target that builds outside of the tree like we are currently doing. We could add a single symbol as a check, drm_core in kernel would not provide the symbol. drm_core compiled as a module provides it. drm compiled out of tree requires it. drm compiled in tree doesn't care.
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
