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
On Thu, 2013-02-28 at 11:31 -0300, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 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.
> >> >
> >> > /va
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:
>
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:
>
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
On Thu, 2013-02-28 at 11:31 -0300, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 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.
> >> >
> >> > /va
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:
>
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
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
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
On Thu, Feb 28, 2013 at 6:59 PM, Sedat Dilek wrote:
> On Thu, Feb 28, 2013 at 6:33 PM, Paulo Zanoni wrote:
>> Hi
>>
>> 2013/2/28 Sedat Dilek :
>>> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek
>>> wrote:
On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni
wrote:
> Hi
>
> 2013/2
On Thu, Feb 28, 2013 at 6:59 PM, Sedat Dilek wrote:
> On Thu, Feb 28, 2013 at 6:33 PM, Paulo Zanoni wrote:
>> Hi
>>
>> 2013/2/28 Sedat Dilek :
>>> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 Chris W
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
>>
On Thu, Feb 28, 2013 at 6:33 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 Sedat Dilek :
>> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
>>> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
Hi
2013/2/28 Chris Wilson :
> On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sedat D
On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
>> Hi
>>
>> 2013/2/28 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,
>
On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 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:
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
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
On Thu, Feb 28, 2013 at 6:33 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 Sedat Dilek :
>> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek
>> wrote:
>>> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
Hi
2013/2/28 Chris Wilson :
> On Thu, Feb 28, 2013 at 12:06:28AM +0100, Sed
On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
>> Hi
>>
>> 2013/2/28 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,
>
On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
> Hi
>
> 2013/2/28 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
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: [
Hi
2013/2/28 Sedat Dilek :
> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
>> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
>>> Hi
>>>
>>> 2013/2/28 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
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 c
Hi
2013/2/28 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_
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
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
On Thu, Feb 28, 2013 at 8:44 AM, Josh Boyer wrote:
> On Thu, Feb 28, 2013 at 8:38 AM, Alex Deucher
> wrote:
>> On Wed, Feb 27, 2013 at 8:14 PM, Josh Boyer wrote:
>>> On Wed, Feb 27, 2013 at 7:01 PM, Josh Boyer wrote:
On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer wrote:
> On Wed, Feb 27
Hi
2013/2/28 Sedat Dilek :
> On Thu, Feb 28, 2013 at 6:12 PM, Sedat Dilek wrote:
>> On Thu, Feb 28, 2013 at 3:31 PM, Paulo Zanoni wrote:
>>> Hi
>>>
>>> 2013/2/28 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
On Thu, Feb 28, 2013 at 8:38 AM, Alex Deucher wrote:
> On Wed, Feb 27, 2013 at 8:14 PM, Josh Boyer wrote:
>> On Wed, Feb 27, 2013 at 7:01 PM, Josh Boyer wrote:
>>> On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer wrote:
On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer wrote:
> On Mon, Feb 25,
On Wed, Feb 27, 2013 at 8:14 PM, Josh Boyer wrote:
> On Wed, Feb 27, 2013 at 7:01 PM, Josh Boyer wrote:
>> On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer wrote:
>>> On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer wrote:
On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie wrote:
> Alex Deucher (29)
Hi
2013/2/28 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_a
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
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
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
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
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
On Wed, Feb 27, 2013 at 7:01 PM, Josh Boyer wrote:
> On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer wrote:
>> On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer wrote:
>>> On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie wrote:
Alex Deucher (29):
drm/radeon: halt engines before disabling MC
On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer wrote:
> On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer wrote:
>> On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie wrote:
>>> Alex Deucher (29):
>>> drm/radeon: halt engines before disabling MC (6xx/7xx)
>>> drm/radeon: halt engines before disabl
On Wed, Feb 27, 2013 at 3:20 PM, Josh Boyer wrote:
> On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer wrote:
>> On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie wrote:
>>> Alex Deucher (29):
>>> drm/radeon: halt engines before disabling MC (6xx/7xx)
>>> drm/radeon: halt engines before disabl
On Wed, Feb 27, 2013 at 11:34 AM, Josh Boyer wrote:
> On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie wrote:
>> Alex Deucher (29):
>> drm/radeon: halt engines before disabling MC (6xx/7xx)
>> drm/radeon: halt engines before disabling MC (evergreen)
>> drm/radeon: halt engines befor
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
On Mon, Feb 25, 2013 at 7:05 PM, Dave Airlie wrote:
> Alex Deucher (29):
> drm/radeon: halt engines before disabling MC (6xx/7xx)
> drm/radeon: halt engines before disabling MC (evergreen)
> drm/radeon: halt engines before disabling MC (cayman/TN)
> drm/radeon: halt engines
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:
>
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:
>
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
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
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
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).
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).
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:
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:
>
> 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
Hi Linus,
This is the main drm pull for the 3.9-rc1 merge, and my chance to have my
email published verbatim as an article by the worst news site ever.
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 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
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
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
57 matches
Mail list logo