Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used
Frans Pop wrote:
On Saturday 23 September 2006 12:45, Attilio Fiandrotti wrote:
Speaking generically, i don't know how much is safe having DFB running
in accelerated mode using fb module "X" on architecture "Y".
An extensive set of tests to detect bad X,Y couples looks dificlut to
be performed, so to be sure the end-user never runs in a bad X,Y
situation, a safe choice would be disabling hw acceleration by defalut,
for all architectures.
On the other hand, that does not really help directfb development...
But I've now changed rootskel-gtk so that no-hardware is set by default
but hardware acceleration can be enabled with directfb/hw-accel=true.
IMHO i still think this was a wise move, since it solves a wide range of
potential problems and the boot time option you introduced still allows
people who want to debug DFB's hw acceleration to do it.
The d-i ISO itself could become a useful tool for directfb developers to
test DFB's HW accelerated functionalities on a wide range of different