Re: DRM function pointer work..

[Keith Whitwell <keith@tungstengraphics.com>]

Ian Romanick wrote:
> 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. :(

Yes, while I support the current rework and de-templatization of the code, I 
don't support any attempt to split the drm modules to try and share code at 
runtime - ie. I don't support a core/submodule approach.

The arguments are pretty much the same as those against unbundling core mesa 
from the drivers - as soon as somebody tries to do an upgrade you're screwed. 
  Anyone trying to run dual head with different 'versions' on each head, 
you're screwed.

The last thing we need right now is a new ABI to worry about.

Keith