On Thu, Oct 24, 2002 at 01:47:01PM +0200, Michel D�nzer wrote: > > That certainly shouldn't be needed for shared entities. Where exactly > > was it crashing ? > > XAA dereferences pScrn->pScreen to track the state of shared entities. > RADEONScreenInit() calls other radeon driver functions which call > info->accel->Sync(), but the driver independent code only sets pScrn->pScreen > after ScreenInit(). Boom. A backtrace would be useful.
> > > Something else I've been wondering is if there's any benefit to having > > > non-DRI DDX drivers in our tree. I'd prefer having the new cursors > > > instead. ;) > > > > Yes, someone may want to start a DRI driver for that chipset. > > For the fbdev, vesa, vga ... drivers? ;) Seriously though, they could > easily add it back then. I was thinking only keeping the absolute > minimum of drivers might cut down on the work needed for merges > slightly, but maybe that's not the case. For drivers that aren't DRI'ified - there are no problems whatsoever, there are never any merge conflicts and for the size of them I'd just leave them were they are. Alan. ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
