[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used



Sven Luther wrote:
On Sat, Sep 23, 2006 at 10:13:10PM +0200, Sven Luther wrote:

On Sat, Sep 23, 2006 at 12:45:10PM +0200, Attilio Fiandrotti wrote:

looking at DFB's supported-hardware page

http://www.directfb.org/index.php?path=Main%2FSupport%2FGraphics

Well, ...

I did some try with my xgi card, and even though i disabled hardware
acceleration, this is a nogo. I ended up in a messed up text terminal (with
black blocks and â chars for the box borders and shadow).

So, it is clear that directfb needs not only the per-card drivers for
acceleration, but also for normal usage.

That said, i couldn't find any kind of directfb log or something, so maybe the
above guess was bad, and something else funny happened, since that was with a
2.6.18 kernel.


DirectFB only supports :

          FB_ACCEL_SIS_GLAMOUR_2
	  FB_ACCEL_SIS_XABRE

While my card is :

	FB_ACCEL_XGI_VOLARI_V

But that is only for accel. I didn't find where the pci ids are checked, but
maybe this is related to the sis->xgi vendor id change.

IIUC, you loaded the per-card (SiS) fb device, but DFB ran unaccelerated because it didn't recognize the board and furthermore acceleration was forced off, right? In this case i wonder where the bug is, in the framebuffer device or in DFB card-indipendent code?
Should we start x-posting on directfb-devel to get an expert help?

Attilio



Reply to: