http://bugs.freedesktop.org/show_bug.cgi?id=18148
--- Comment #11 from Michal Suchanek
It would definitely be nice to have that, but that's no excuse to have this bad behaviour.
Lots of things can be done, if the driver find outs the virtual size is too big, well then why not change the virtual size?
If you want to be puristic and avoid workarounds then disable EXA when the virtual size is too big, or fail completely and return an error.
Having the user wondering why on earth everything is so painfully is low is Not Good(tm).
As explained in comment #6 X is not designed for that either. The memory is divided among several subsystems which are initialized sequentially and do not know about the memory requirements of each other. It would require either some guess which might cause problems in some special cases again or substantial changes to the X configuration and module initialization process. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org