Re: (another) Intel driver change needs testing.

2010-07-07 Thread Ted Roby
On Fri, May 28, 2010 at 9:47 AM, Ted Roby wrote: > > > On Tue, May 18, 2010 at 11:01 AM, Ted Roby wrote: > >> Here's a screenshot: >> http://devio.us/~roby/images/artifact001.jpg >> > > The artifact is still present in -current. > However, it occurs much less frequently. > This artifact no lon

Re: (another) Intel driver change needs testing.

2010-05-28 Thread Ted Roby
On Tue, May 18, 2010 at 11:01 AM, Ted Roby wrote: > I can re-create this artifact by alt-tabbing between another > non-fullscreen window, and the pidgin IM (message) window. > Tabbing between fullscreen mozilla-firefox and then pidgin IM > window clears the bug. Tabbing between non-fullscreen >

Re: (another) Intel driver change needs testing.

2010-05-26 Thread Stuart Henderson
On 2010/05/26 15:04, J.C. Roberts wrote: > On Tue, 25 May 2010 21:21:49 -0700 Philip Guenther > wrote: > > > > On Sun, May 23, 2010 at 10:57 PM, J.C. Roberts > > wrote: ... > > > I found the problem. The 'xorg' vendor branch was treated as 'HEAD' > > > for a while, but subsequently moving 'HEAD'

Re: (another) Intel driver change needs testing.

2010-05-26 Thread J.C. Roberts
On Tue, 25 May 2010 21:21:49 -0700 Philip Guenther wrote: > > On Sun, May 23, 2010 at 10:57 PM, J.C. Roberts > wrote: ... > > I found the problem. The 'xorg' vendor branch was treated as 'HEAD' > > for a while, but subsequently moving 'HEAD' back over to the 'MAIN' > > branch has broken date limi

Re: (another) Intel driver change needs testing.

2010-05-26 Thread Philip Guenther
On Wed, May 26, 2010 at 3:04 PM, J.C. Roberts wrote: > On Tue, 25 May 2010 21:21:49 -0700 Philip Guenther > wrote: ... >> What is "MAIN"? Where is it documented? > > Here: > http://www.openbsd.org/cgi-bin/cvsweb/xenocara/proto/x11proto/keysym.h > > I don't know where the documentation for the "M

Re: (another) Intel driver change needs testing.

2010-05-25 Thread Philip Guenther
On Sun, May 23, 2010 at 10:57 PM, J.C. Roberts wrote: ... > I found the problem. The 'xorg' vendor branch was treated as 'HEAD' > for a while, but subsequently moving 'HEAD' back over to the 'MAIN' > branch has broken date limited checkouts of 'HEAD'. Instead of > getting what was HEAD at the spe

Re: (another) Intel driver change needs testing.

2010-05-23 Thread J.C. Roberts
On Sun, 23 May 2010 15:53:57 -0700 "J.C. Roberts" wrote: > Since it seems I'm the first to find a problem with the '-D' flag, I'm > testing to see if it is being caused by my using the ISO date_spec > format by doing a similar checkout with the "Internet" date_spec > format. i.e. > > # rm -

Re: (another) Intel driver change needs testing.

2010-05-23 Thread J.C. Roberts
On Sun, 23 May 2010 17:19:03 +0100 Owain Ainsworth wrote: > On Sun, May 23, 2010 at 10:15:21AM -0600, Ted Roby wrote: > > On Sun, May 23, 2010 at 9:55 AM, Owain Ainsworth > > wrote: > > > > > > > > > > > > > > You mean that the build failed? or that the corruption happened? > > > > > > > > I mean

Re: (another) Intel driver change needs testing.

2010-05-23 Thread Owain Ainsworth
On Sun, May 23, 2010 at 10:15:21AM -0600, Ted Roby wrote: > On Sun, May 23, 2010 at 9:55 AM, Owain Ainsworth wrote: > > > > > > > > > You mean that the build failed? or that the corruption happened? > > > > > I mean the Xenocara and kernel builds fail, depending. > I have used 'log' to replace i91

Re: (another) Intel driver change needs testing.

2010-05-23 Thread Ted Roby
On Sun, May 23, 2010 at 9:55 AM, Owain Ainsworth wrote: > > > > You mean that the build failed? or that the corruption happened? > > I mean the Xenocara and kernel builds fail, depending. I have used 'log' to replace i915_drv.h when it was changed as well. I got lucky catching the April 24 snapsh

Re: (another) Intel driver change needs testing.

2010-05-23 Thread Owain Ainsworth
On Sun, May 23, 2010 at 09:09:56AM -0600, Ted Roby wrote: > On Tue, May 18, 2010 at 5:45 PM, Owain Ainsworth wrote: > > > > > Can you please use cvs to bisect which commit caused the problem? (it is > > only three commits, will not take long). It may help me fix it to know > > what caused it. > >

Re: (another) Intel driver change needs testing.

2010-05-23 Thread Ted Roby
On Tue, May 18, 2010 at 5:45 PM, Owain Ainsworth wrote: > > Can you please use cvs to bisect which commit caused the problem? (it is > only three commits, will not take long). It may help me fix it to know > what caused it. > > Sorry for the late reply. I can confirm the following: The problem d

Re: (another) Intel driver change needs testing.

2010-05-19 Thread J.C. Roberts
On Wed, 19 May 2010 09:36:14 +0200 David Coppa wrote: > > That's good news! I don't have the "experimental" mesa patch, but > > if you want me to test it, mail it to me off list. > > I've spoken too soon! > The problem now has changed, but it's still here. > > Now the screen goes blank but not t

Re: (another) Intel driver change needs testing.

2010-05-19 Thread J.C. Roberts
On Wed, 19 May 2010 20:10:49 +0200 (CEST) Mark Kettenis wrote: > > When testing code controlling video/graphics hardware, you should > > power off the system after hitting an error. The reason is simple; > > the hardware/memory is no longer in a know state, so you no longer > > know what you are t

Re: (another) Intel driver change needs testing.

2010-05-19 Thread Mark Kettenis
> Date: Wed, 19 May 2010 09:30:22 -0700 > From: "J.C. Roberts" > > On Wed, 19 May 2010 09:36:14 +0200 David Coppa wrote: > > > > The occasional/intermittent screen corruption bug seems to have > > > > disappeared for me with latest xenocara -current + the > > > > "experimental" Mesa 7.8 update.

Re: (another) Intel driver change needs testing.

2010-05-19 Thread J.C. Roberts
On Wed, 19 May 2010 09:36:14 +0200 David Coppa wrote: > > > The occasional/intermittent screen corruption bug seems to have > > > disappeared for me with latest xenocara -current + the > > > "experimental" Mesa 7.8 update. > > > > That's good news! I don't have the "experimental" mesa patch, but

Re: (another) Intel driver change needs testing.

2010-05-19 Thread David Coppa
On Tue, 18 May 2010, J.C. Roberts wrote: > On Tue, 18 May 2010 16:52:11 +0200 David Coppa wrote: > > On Tue, May 18, 2010 at 4:40 PM, J.C. Roberts > > wrote: > > > > > Whether enabled or disabled in xorg.conf, (so far) it seems to have > > > no effect on the occasional/intermittent screen corru

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Owain Ainsworth
On Tue, May 18, 2010 at 05:42:09PM -0600, Ted Roby wrote: > On Tue, May 18, 2010 at 5:25 PM, Owain Ainsworth wrote: > > > > > I was referring to which of the three drm commits on the 10th. > > > > > Oh. They were all applied. > Unfortunately, I built everything late that night and early on the 11t

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Ted Roby
On Tue, May 18, 2010 at 5:25 PM, Owain Ainsworth wrote: > > I was referring to which of the three drm commits on the 10th. > > Oh. They were all applied. Unfortunately, I built everything late that night and early on the 11th. So, I never determined which patch caused it. I was watching with grea

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Owain Ainsworth
On Tue, May 18, 2010 at 05:02:42PM -0600, Ted Roby wrote: > > > > There were three, could you confirm which one you mean? > > > > > (II) Loading extension GLX > (II) LoadModule: "intel" > (II) Loading /usr/X11R6/lib/modules/ > drivers//intel_drv.so > (II) Module intel: vendor="X.Org Foundation" >

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Ted Roby
On Tue, May 18, 2010 at 3:04 PM, Owain Ainsworth wrote: > > > absinthe-minded? > > > > Hard to get decent Absinthe in the UK, i'm afraid. > > Sorry. > > There were three, could you confirm which one you mean? > > (II) Loading extension GLX (II) LoadModule: "intel" (II) Loading /usr/X11R6/lib/mod

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Sviatoslav Chagaev
On Mon, 17 May 2010 22:16:54 +0100 Owain Ainsworth wrote: > The diff found at http://xenocara.org/xvmc.diff could do with some > testing. > > This is some stuff that I didn't backport back to 2.9.1 when I did the > intial intel driver backport pile. This contains a huge cleanup of the > XVMC cod

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Owain Ainsworth
On Tue, May 18, 2010 at 07:40:23AM -0700, J.C. Roberts wrote: > On Mon, 17 May 2010 22:16:54 +0100 Owain Ainsworth > wrote: > > For those of you new here, or termnally adsent minded, instructions > > follow: > > > > You've got be careful with those "termnally adsent" folks. ;) Feh, typo ;). >

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Owain Ainsworth
On Tue, May 18, 2010 at 11:01:29AM -0600, Ted Roby wrote: > On Tue, May 18, 2010 at 8:40 AM, J.C. Roberts wrote: > > > On Mon, 17 May 2010 22:16:54 +0100 Owain Ainsworth > > wrote: > > > For those of you new here, or termnally adsent minded, instructions > > > follow: > > > > > > > You've got be

Re: (another) Intel driver change needs testing.

2010-05-18 Thread J.C. Roberts
On Tue, 18 May 2010 07:40:23 -0700 "J.C. Roberts" wrote: > It seems to become enabled, but really doesn't do anything. > > (II) intel(0): DPMS enabled > (==) intel(0): Intel XvMC decoder disabled copy-n-paste snafu. should read "enabl

Re: (another) Intel driver change needs testing.

2010-05-18 Thread J.C. Roberts
On Tue, 18 May 2010 16:52:11 +0200 David Coppa wrote: > On Tue, May 18, 2010 at 4:40 PM, J.C. Roberts > wrote: > > > Whether enabled or disabled in xorg.conf, (so far) it seems to have > > no effect on the occasional/intermittent screen corruption bug seen > > by dcoppa (915GM) and me (845G). >

Re: (another) Intel driver change needs testing.

2010-05-18 Thread Ted Roby
On Tue, May 18, 2010 at 8:40 AM, J.C. Roberts wrote: > On Mon, 17 May 2010 22:16:54 +0100 Owain Ainsworth > wrote: > > For those of you new here, or termnally adsent minded, instructions > > follow: > > > > You've got be careful with those "termnally adsent" folks. ;) > > absinthe-minded? > >

Re: (another) Intel driver change needs testing.

2010-05-18 Thread David Coppa
On Tue, May 18, 2010 at 4:40 PM, J.C. Roberts wrote: > Whether enabled or disabled in xorg.conf, (so far) it seems to have no > effect on the occasional/intermittent screen corruption bug seen by > dcoppa (915GM) and me (845G). The occasional/intermittent screen corruption bug seems to have disa

Re: (another) Intel driver change needs testing.

2010-05-18 Thread J.C. Roberts
On Mon, 17 May 2010 22:16:54 +0100 Owain Ainsworth wrote: > For those of you new here, or termnally adsent minded, instructions > follow: > You've got be careful with those "termnally adsent" folks. ;) With the 845G and a minimal xorg.conf (only "NoTrapSignals") I get the expected: (II

Re: (another) Intel driver change needs testing.

2010-05-17 Thread Marco Peereboom
(==) intel(0): Intel XvMC decoder enabled (II) intel(0): Set up textured video (II) intel(0): [XvMC] xvmc_vld driver initialized. (II) intel(0): direct rendering: DRI2 Enabled groovy,... up to the second amd64 on gcc4. On Mon, May 17, 2010 at 10:16:54PM +0100, Owain Ainsworth wrote: > The diff f

Re: (another) Intel driver change needs testing.

2010-05-17 Thread Dave Del Debbio
I applied the patch. It shows up as expected: (**) intel(0): DPMS enabled (==) intel(0): Intel XvMC decoder enabled (II) intel(0): Set up textured video (II) intel(0): [XvMC] xvmc_vld driver initialized. Is there anything else you want done to test? I am not aware of any package (such as mplaye

(another) Intel driver change needs testing.

2010-05-17 Thread Owain Ainsworth
The diff found at http://xenocara.org/xvmc.diff could do with some testing. This is some stuff that I didn't backport back to 2.9.1 when I did the intial intel driver backport pile. This contains a huge cleanup of the XVMC code (and enabled it on 965+ by default, it is still there by an option on