On Tue, 2005-03-15 at 11:53 -0500, Dave Jones wrote: > On Tue, Mar 15, 2005 at 04:15:42PM +0000, Dave Airlie wrote: > > > > > > > > > > I might get time to do a code review, my main worry is that all the > > > > problems reported with those patches in -mm made it into the patchset > that > > > > went into Linus.. mainly things like forgetting to memset certain > > > > structures to 0 and sillies like that... > > > > > > I saw one report where the recent drm security hole fix broke dri > > > for one user. Whilst it seems an isolated incident, could this have > > > more impact than we first realised ? > > > > the radeon security changes? I've gotten no bad feedback on those neither > > has dri-devel, so I've assumed they were all fine (usually radeon bug > > reports get back fairly quickly as everyone has one ..), > > > > the multi-bridge stuff is definitely broken as I've seen radeon and r128 > > reports on it .. and it looks most like 2.6.11-bk2 broke things and I > > haven't merged anything until -bk7 ... > > Wait, -bk2 broke things ? The big agp changes went into -bk3, > so this seems odd. >
To clarify. 2.6.11-bk2 is working fine. It broke with 2.6.11-bk3, where IIRC a drm update was made. Disabling DRI in X and/or DRM in the kernel prevents X from locking the machine. > Dave > Cheers, Andrew ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
