On 4 Sep, Owen Taylor wrote:
>
> [EMAIL PROTECTED] writes:
>
>
>> These are not reasonable for the bulk of users who want to use
>> pre-compiled X server and module from some distribution. Perhaps we
>> should look at some X startup options instead of compile time options
>> for this code. This would then enable the mode that would best match
>> what I do: an X server that uses software 3D even on hardware capable of
>> hardware 3D via DRI. The gaming and other 3D users would consider this
>> totally absurd. I don't need frames per second because I am generating
>> scenes and manipulating 2D images.
>
> Well, you certainly don't have to recompile to turn off DRI, just turn
> off the options in your XF86Config. To get a command line option,
> you could use the -xf86config option to XFree86 and switch between
> two config files.
>
>
Unfortunately, you do have to recompile to turn off the "gobble most ram
for 3D". I've looked at the code in a few drivers. The gobble logic is
controlled by the compile time #ifdef's, not by the XFConfig switches.
So if your binary was compiled with DRI capability, it will gobble
regardless of whether the XFConfig loads DRI modules. It is probably
impossible to coordinate the kernel module's hardware access with the X
server while having dynamic allocation and de-allocation. It may be
feasible to be startup switch controlled because this is in the same
stretch of logic that is establishing the other configuration controlled
parameters.
Hence my interest in changing the server modules to use config switches
rather than compile time switches. (This will sit on some back burner
if nobody else gets around to it.)
R Horn
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
