http://bugs.freedesktop.org/show_bug.cgi?id=5092





------- Comment #22 from [EMAIL PROTECTED]  2007-06-28 11:52 PST -------
Hi.

The IRQ issue on K8M800 has been around for ages. I'm not saying it can't be
fixed (sometimes when my K8M800 has been running for quite some time it will
work nicely), but trying to initialize it from scratch it always fails. The
reason is that K8M800 fires a huge amount of spurious interrupts.

If irq debug is turned off, the handler slows down the machine considerably
trying to handle the interrupts.

The problem is probably a hardware bug. The same problem occurs on certain
variants of KM400. I once asked via about it and they claimed that IRQ
functionality was never verified on these chips since they didn't do video
capture. Hence no use for IRQs in VIAs windows drivers.

The only sane thing to do is to not enable IRQs for these chips.

Regarding the texture lockup issue, 
the same code works much better on other chips with the same 3D engine. 
It might just be a memory timing issue on K8M800, which means that tracking it
down using software can be very difficult.

/Thomas


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to