On Tue, 2002-09-24 at 17:08, Michel Dänzer wrote:
> On Die, 2002-09-24 at 10:08, Eric Anholt wrote: 
> > On Mon, 2002-09-23 at 09:00, Michel Dänzer wrote:
> > 
> > > I've incorporated this and turned it into a template:
> > > 
> > > http://penguinppc.org/~daenzer/DRI/drm-vblank-template.diff
> > 
> > I've put a new one up at
> > http://people.freebsd.org/~anholt/dri/files/framethrottle2.diff
> > which includes MGA support.  I'll work on r128 when I get some time
> > again.  I may have reversed the IRQ_ACTIVE -> IRQ_NR change
> > inadvertently, I/we can change that back.  Sleep is my top priority
> > right now.
> 
> Yeah, let's iron this out and get it committed; I'll leave the BSD, mga, r200
> and whatnot bits to you. :) BTW is there any reason why the mga stuff can't move
> to the shared DRM directory?

Which mga stuff?  MGA is shared about as much as the other drivers.

One thing we should do is share drm.h between the two.

> What about using LIBGL_THROTTLE_REFRESH in all 3D drivers?
> 
> I've updated my patch.

Sounds good to me.

> BTW I'm just experiencing IRQ timeouts as well. In fact, no interrupts
> occur at all, and the RADEON_GEN_INT_STATUS register seems to always
> contain 0x00080007; interestingly, bit 16 isn't documented. Maybe that's
> just a red herring though, and the IRQ is disabled in PCI config space
> or something?

How often do you get timeouts?  Does it happen with any app?  I haven't
noticed any yet.

-- 
Eric Anholt <[EMAIL PROTECTED]>
http://people.freebsd.org/~anholt/dri/




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to