--- Michel D�nzer <[EMAIL PROTECTED]> wrote: > On Wed, 2003-06-11 at 21:47, Alex Deucher wrote: > > I've had several reports of DRI not working after a screen resize > using > > mergedfb code. I haven't really had time to tackle it, and > > unfortunately, i'm not real familiar with how DRI interacts with a > mode > > change or xrandr. > > AFAIK it doesn't care about them at all yet (and it shouldn't need to > for the former at least). > >
that's what I thought. > > As background, mergedfb provides a single framebuffer with two > > viewports looking into it. HW accelerated 3D works fine on both > heads > > in the inital mode, however I've gotten reports from users that the > DRI > > stops working when you change "metamodes" using ctrl-alt-+/-. > > metamodes are just mode combinations that describe the mode on each > > head for mode changes (e.g., 1024x768-1024x768 1024x768-800x600, > etc.). > > > > More details about the problem are listed here: > > http://bugs.xfree86.org/cgi-bin/bugzilla/show_bug.cgi?id=276 > > Looks like the hanging ioctl is DRM_IOCTL_LOCK, maybe there's a > DRILock() > with no corresponding DRIUnlock()? > Maybe... I don't know. I certainly didn't add or remove any when wrote mergedfb support. I don't know why it wouldn't also show up in single head mode... Alex __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
