Date: Wed, 25 Mar 2009 09:29:04 +0000 From: "N.J. Mann" <njm@njm.me.uk> To: Robert Noland <rnoland@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r190401 - head/sys/dev/drm Message-ID: <20090325092904.GA2801@titania.njm.me.uk> In-Reply-To: <200903250150.n2P1ou4g062376@svn.freebsd.org> References: <200903250150.n2P1ou4g062376@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200903250150.n2P1ou4g062376@svn.freebsd.org>, Robert Noland (rnoland@FreeBSD.org) wrote: > Author: rnoland > Date: Wed Mar 25 01:50:56 2009 > New Revision: 190401 > URL: http://svn.freebsd.org/changeset/base/190401 > > Log: > Rework the management of vblank interrupts a bit. > > When a vt switch occurs the irq handler is uninstalled. Interrupts > and the state tracking of what was enabled/disabled wasn't working > properly. This should resolve the reports of "slow windows" after a > vt switch, among other things. The radeon 2d driver seems to work a > bit more correctly than the Intel driver. With the Intel driver, > vblank interrupts will be enabled at system startup and will only > be disabled after an additional modeset (vt switch, dpms, randr event). > > With this patch, I am able to run glxgears synced to vblank and > vt switch while it is running without ill effects. > > MFC after: 3 days > > Modified: > head/sys/dev/drm/drm_irq.c Is this a possible cure for the problem I reported here: http://lists.freebsd.org/pipermail/freebsd-x11/2009-February/007670.html Cheers, Nick. --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090325092904.GA2801>