Re: [git pull] drm merge for 3.9-rc1

2013-03-05 Thread Josh Boyer
On Thu, Feb 28, 2013 at 1:59 PM, Josh Boyer wrote: > On Thu, Feb 28, 2013 at 10:15 AM, Josh Boyer wrote: >> On Thu, Feb 28, 2013 at 10:09 AM, Alex Deucher wrote: >>> On Thu, Feb 28, 2013 at 8:44 AM, Josh Boyer wrote: On Thu, Feb 28, 2013 at 8:38 AM, Alex Deucher wrote: > ca5

Re: [git pull] drm merge for 3.9-rc1

2013-03-05 Thread Daniel Vetter
On Tue, Feb 26, 2013 at 05:39:46PM -0800, Linus Torvalds wrote: > On Mon, Feb 25, 2013 at 4:05 PM, Dave Airlie wrote: > > > > Highlights: > > > > i915: all over the map, haswell power well enhancements, valleyview macro > > horrors cleaned up, killing lots of legacy GTT > > code, > > Lowlight: >

Re: [git pull] drm merge for 3.9-rc1

2013-03-05 Thread Alex Deucher
On Tue, Mar 5, 2013 at 10:21 AM, Josh Boyer wrote: > On Thu, Feb 28, 2013 at 1:59 PM, Josh Boyer wrote: >> On Thu, Feb 28, 2013 at 10:15 AM, Josh Boyer wrote: >>> On Thu, Feb 28, 2013 at 10:09 AM, Alex Deucher >>> wrote: On Thu, Feb 28, 2013 at 8:44 AM, Josh Boyer wrote: > On Thu, Fe

Re: [git pull] drm merge for 3.9-rc1

2013-03-03 Thread Azat Khuzhin
On Wed, Feb 27, 2013 at 5:39 AM, Linus Torvalds wrote: > On Mon, Feb 25, 2013 at 4:05 PM, Dave Airlie wrote: >> >> Highlights: >> >> i915: all over the map, haswell power well enhancements, valleyview macro >> horrors cleaned up, killing lots of legacy GTT >> code, > > Lowlight: > > There's some

Re: [git pull] drm merge for 3.9-rc1

2013-03-01 Thread Josh Boyer
On Thu, Feb 28, 2013 at 10:15 AM, Josh Boyer wrote: > On Thu, Feb 28, 2013 at 10:09 AM, Alex Deucher wrote: >> On Thu, Feb 28, 2013 at 8:44 AM, Josh Boyer wrote: >>> On Thu, Feb 28, 2013 at 8:38 AM, Alex Deucher wrote: ca57802e521de54341efc8a56f70571f79ffac72 is the first bad commit >>

Re: [git pull] drm merge for 3.9-rc1

2013-03-01 Thread Sedat Dilek
On Thu, Feb 28, 2013 at 12:18 PM, Chris Wilson wrote: > On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote: >> On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote: >> > Hi, >> > >> > I am seeing this also on Linux-Next. >> > >> > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.20

Re: [git pull] drm merge for 3.9-rc1

2013-03-01 Thread Josh Boyer
On Thu, Feb 28, 2013 at 10:09 AM, Alex Deucher wrote: > On Thu, Feb 28, 2013 at 8:44 AM, Josh Boyer wrote: >> On Thu, Feb 28, 2013 at 8:38 AM, Alex Deucher wrote: >>> ca57802e521de54341efc8a56f70571f79ffac72 is the first bad commit >> >> So I don't think that's actually the cause of

Re: [git pull] drm merge for 3.9-rc1

2013-02-28 Thread Chris Wilson
On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat Dilek wrote: > On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote: > > Hi, > > > > I am seeing this also on Linux-Next. > > > > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.202381] > > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did no

Re: [git pull] drm merge for 3.9-rc1

2013-02-28 Thread Sedat Dilek
On Wed, Feb 27, 2013 at 11:36 PM, Sedat Dilek wrote: > Hi, > > I am seeing this also on Linux-Next. > > /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.202381] > [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout > (has irq: 1)! > /var/log/kern.log:Feb 27 22:52:35 fambox

Re: [git pull] drm merge for 3.9-rc1

2013-02-28 Thread Sedat Dilek
Hi, I am seeing this also on Linux-Next. /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.202381] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout (has irq: 1)! /var/log/kern.log:Feb 27 22:52:35 fambox kernel: [ 28.210588] [drm:intel_dp_aux_wait_done] *ERROR* dp aux

Re: [git pull] drm merge for 3.9-rc1

2013-02-27 Thread Chris Wilson
On Tue, Feb 26, 2013 at 05:39:46PM -0800, Linus Torvalds wrote: > On Mon, Feb 25, 2013 at 4:05 PM, Dave Airlie wrote: > > > > Highlights: > > > > i915: all over the map, haswell power well enhancements, valleyview macro > > horrors cleaned up, killing lots of legacy GTT > > code, > > Lowlight: >

Re: [git pull] drm merge for 3.9-rc1

2013-02-26 Thread Linus Torvalds
On Tue, Feb 26, 2013 at 7:30 PM, Dave Airlie wrote: > > If you want to just bump it so Ironlake isn't affected, (patch attached). It works fine 95% of the time and isn't a hard failure when it doesn't, so this isn't critical. I can wait for it to be fixed a while. > Is this external DP monitor o

Re: [git pull] drm merge for 3.9-rc1

2013-02-26 Thread Dave Airlie
On Wed, Feb 27, 2013 at 11:39 AM, Linus Torvalds wrote: > On Mon, Feb 25, 2013 at 4:05 PM, Dave Airlie wrote: >> >> Highlights: >> >> i915: all over the map, haswell power well enhancements, valleyview macro >> horrors cleaned up, killing lots of legacy GTT >> code, > > Lowlight: > > There's som

Re: [git pull] drm merge for 3.9-rc1

2013-02-26 Thread Linus Torvalds
On Tue, Feb 26, 2013 at 5:39 PM, Linus Torvalds wrote: > > Lowlight: > > [5.710827] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not > signal timeout (has irq: 1)! Oh, forgot to mention - this is my trusty old Westmere chip (aka "Core i5-670", aka Clarkdale, aka GMA-some-random-number).

Re: [git pull] drm merge for 3.9-rc1

2013-02-26 Thread Linus Torvalds
On Mon, Feb 25, 2013 at 4:05 PM, Dave Airlie wrote: > > Highlights: > > i915: all over the map, haswell power well enhancements, valleyview macro > horrors cleaned up, killing lots of legacy GTT > code, Lowlight: There's something wrong with i915 DP detection or whatever. I get stuff like this:

Re: [git pull] drm merge for 3.9-rc1

2013-02-25 Thread Dave Airlie
> > I did the fun conflict resolution, so my tree doesn't have the ordering > changes. > > I also did some things slightly differently from you - you had left > some direct ib[] accesses that I spotted (see for example "case 0x48" > (aka "Copy L2T Frame to Field"), and yours apparently has a few c

Re: [git pull] drm merge for 3.9-rc1

2013-02-25 Thread Linus Torvalds
On Mon, Feb 25, 2013 at 4:05 PM, Dave Airlie wrote: > > So up front, this has a massive merge conflict in > drivers/gpu/drm/radeon/evergreen_cs.c I've fixed it up in drm-next-merged > in the same tree, I fixed up some small ordering issues in my merge as > well, however they aren't important if yo