On Mon, 2003-07-28 at 18:52, Ian Romanick wrote:
Michel Dänzer wrote:
On Sun, 2003-07-27 at 00:54, Ian Romanick wrote:
We also need a way to specify that interrupts are not available. In this case, we don't want to export any of the vsync related GLX extensions.
The only way to find out is to try the ioctl, so maybe try it in CreateContext() and set VBLANK_FLAG_NO_IRQ if it fails?
My point is that rmesa->do_irqs has nothing to do with this.
Why not? do_irqs gets set in three cases:
1. The kernel version was too low to query for an IRQ number.
2. The kernel version was high enough to query for an IRQ number, but none was reported.
3. The user specifically asks that interrupts not be used, for whatever reason.
These are all about SW interrupts, they don't say anything about vblank.
Okay. As per our discussion in IRC today, you've convinced me. :) We should revert to the pre-texmem method of just examining rmesa->r200Screen->irq.
Is there any truth to the rumor that IRQ values can be 0 in 2.6? If that is the case, we'll need to make some changes in our drivers. The old code (and the current code) uses and IRQ value of 0 to mean "no interrupt available."
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
