Re: [PATCH, RFC] stop neutering DRI

[Jeremy Katz <katzj redhat com>]

On Mon, 2008-04-07 at 18:15 -0400, Bill Nottingham wrote:
> The attached patch makes anaconda stop neutering DRI/DRM (at least it should.)
> It does it by including the DRI userspace modules (from mesa) and the kernel
> DRM drivers.
> 
> Why do this?
> 
> To be more like the 'normal' installed system. Heck, if DRI's going to fail,
> the system's just going to blow up on the first boot anyway. Furthermore,
> there are cards/chips that do 2D accel via the 3D pipeline.

So, I'm not fundamentally against doing this, but doing it right now is
a little scary.  ajax -- any thoughts from your end?

> Plus, if we want to actually disable it in anaconda, we should do it
> explicitly, not by accident as a consequence of some files not being
> there.

Bleah, we used to, but as the X configuration stack has changed over
time, we've lost those bits I suspect.

> Caveats:
> - listing the kernel drivers explicitly is a hack

I wonder if we'd be better with the (still a hack, but at least not a
list of drivers) bit to do =drm and then map that to everything under
drivers/char/drm

> - this doesn't pull libGL onto the second stage. Assuming nothing dlopens()
>   it, that shouldn't be a problem

The DRI modules static link libGL, so this might be a problem.  Also,
given that the dri modules are statically linked, it's going to be a not
insubstantial space jump.  From a quick test, mksquashfs /usr/lib/dri is
11 megs which is 10% of the size of stage2.  Which isn't necessarily the
end of the world, but it just continues to creep up various things.  It
might also make stage2 + kernel + initrd no longer fit on a 128 meg usb
key

Jeremy