https://bugzilla.kernel.org/show_bug.cgi?id=47351
Nick changed:
What|Removed |Added
CC||ka.n...@mail.ru
--- Comment #7 from Nick 201
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #4 from Nick 2013-04-30 11:53:07 ---
Created an attachment (id=100301)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100301)
dmesg output
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- Yo
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #5 from Nick 2013-04-30 11:53:33 ---
Created an attachment (id=100311)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100311)
Xorg.0.log
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #29 from Hristo Venev ---
I just noticed a regression: the GPU halts when cold boot was done by fglrx and
driver is switched to radeon.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #6 from Nick 2013-04-30 12:14:25 ---
(In reply to comment #3)
> (In reply to comment #0)
> > After upgrading my AMD E-450-based notebook to a newer one (HP 4545s
> > A4-3300-based) i noticed that in spite of noticeable higher cloc
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #8 from Alex Deucher 2013-04-30 12:57:39
---
(In reply to comment #7)
> Yes, I'm quite sure my laptop is mux-less, so I guess the card actually works
> but cannot output anything...
> I've 1.13.4 installed (and 1.14.1 is availab
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #9 from Nick 2013-04-30 13:18:22 ---
Thank you!
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #7 from Michel Dänzer 2013-04-30 13:32:46 ---
Does not enabling Option "BackingStore" in xorg.conf help?
The high power usage might be due to the discrete GPU being powered on, but the
X server isn't using it, so it doesn't help
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Sun, Apr 28, 2013 at 07:04:07PM +0200, Maarten Lankhorst wrote:
> Changes since RFC patch v1:
> - Updated to use atomic_long instead of atomic, since the reservation_id was
> a long.
> - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
> - removed mutex_locked_set_reservation_i
https://bugs.freedesktop.org/show_bug.cgi?id=59592
--- Comment #10 from n...@detonation.org ---
Sorry for the late reply. Took me some time to get my test setup working after
a distribution upgrade. It seems like your patch does indeed fix the problem.
I've played around with FlightGear for severa
On Mon, Apr 29, 2013 at 12:31 PM, Dave Airlie wrote:
>> The reason we (currently) use the dumb buffer interface is because it
>> does pretty much exactly what we need it to, as we only want linear
>> RGB buffers:
>
> Except in the cases where it doesn't do what you want, and possibly in
> the futu
On Wed, Apr 24, 2013 at 06:52:33PM +0300, ville.syrj...@linux.intel.com wrote:
> Here's the latest version of my plane clipping stuff.
>
> I think it should be ready for merging. Laurent reviewed the first patch,
> and Chris reviewed the whole set.
>
> I didn't hear any bikeshedding about the loc
>> Except in the cases where it doesn't do what you want, and possibly in
>> the future where it does less of what you want. You've started on a
>> slippery slope, and I'm stopping you before you make things worse.
>>
>> You are going to have to get SoC kernel drivers to add an ioctl that
>> you ca
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Tue, Apr 30, 2013 at 10:19 PM, Dave Airlie wrote:
>>> Except in the cases where it doesn't do what you want, and possibly in
>>> the future where it does less of what you want. You've started on a
>>> slippery slope, and I'm stopping you before you make things worse.
>>>
>>> You are going to ha
https://bugs.freedesktop.org/show_bug.cgi?id=60553
Laurent carlier changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=64096
Priority: medium
Bug ID: 64096
Assignee: dri-devel@lists.freedesktop.org
Summary: LLVM RV790 etqw regression since R600: Packetize
instructions
Severity: normal
Classific
https://bugs.freedesktop.org/show_bug.cgi?id=64096
--- Comment #1 from Andy Furniss ---
Testing further some of the mesa demos are also wrong - not that I have re-
bisected, just assume same issue, on heads -
gloss = blank.
gears, fbo_firecube, gearbox = too dark.
shadowtex = shadow misaligned
Hi,
In radeon_atombios.c file, radeon_atombios_parse_power_table_6
function, the power state is selected using the state array index:
power_state = (union pplib_power_state *)&state_array->states[i];
The state array has variable sized states which size should be
computed as said in the atombios.
https://bugs.freedesktop.org/show_bug.cgi?id=64099
Priority: medium
Bug ID: 64099
Assignee: dri-devel@lists.freedesktop.org
Summary: Mesa 9.0.3 implementation error: In
_mesa_DeleteHashTable, found non-freed data
Severity: mi
From: Dave Airlie
Sometimes that extra semicolon can really be hard to spot.
Cc: Imre Deak
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_dmabuf.c
b/drivers/gpu/drm/i915/i
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_reg.h between commit a65851af5938 ("drm/i915:
Make data/link N value power of two") from the drm tree and commit
72419203cab9 ("drm/i915: hw state readout support for fdi m/n") from the
drm-intel tre
Since we ask the dmabuf owner to map the dma-buf into our device
address space, but for udl at present that is the CPU address space,
since we don't DMA directly from the mapped buffer.
However if we don't set a dma mask on the usb device, the mapping
ends up using swiotlb on machines that have it
https://bugzilla.kernel.org/show_bug.cgi?id=47351
Nick changed:
What|Removed |Added
CC||ka.n...@mail.ru
--- Comment #7 from Nick 201
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #4 from Nick 2013-04-30 11:53:07 ---
Created an attachment (id=100301)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100301)
dmesg output
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- Yo
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #5 from Nick 2013-04-30 11:53:33 ---
Created an attachment (id=100311)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100311)
Xorg.0.log
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #29 from Hristo Venev ---
I just noticed a regression: the GPU halts when cold boot was done by fglrx and
driver is switched to radeon.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #6 from Nick 2013-04-30 12:14:25 ---
(In reply to comment #3)
> (In reply to comment #0)
> > After upgrading my AMD E-450-based notebook to a newer one (HP 4545s
> > A4-3300-based) i noticed that in spite of noticeable higher cloc
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #8 from Alex Deucher 2013-04-30 12:57:39
---
(In reply to comment #7)
> Yes, I'm quite sure my laptop is mux-less, so I guess the card actually works
> but cannot output anything...
> I've 1.13.4 installed (and 1.14.1 is availab
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #9 from Nick 2013-04-30 13:18:22 ---
Thank you!
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #7 from Michel Dänzer 2013-04-30 13:32:46 ---
Does not enabling Option "BackingStore" in xorg.conf help?
The high power usage might be due to the discrete GPU being powered on, but the
X server isn't using it, so it doesn't help
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Sun, Apr 28, 2013 at 07:04:07PM +0200, Maarten Lankhorst wrote:
> Changes since RFC patch v1:
> - Updated to use atomic_long instead of atomic, since the reservation_id was
> a long.
> - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
> - removed mutex_locked_set_reservation_i
https://bugs.freedesktop.org/show_bug.cgi?id=59592
--- Comment #10 from n...@detonation.org ---
Sorry for the late reply. Took me some time to get my test setup working after
a distribution upgrade. It seems like your patch does indeed fix the problem.
I've played around with FlightGear for severa
On Mon, Apr 29, 2013 at 12:31 PM, Dave Airlie wrote:
>> The reason we (currently) use the dumb buffer interface is because it
>> does pretty much exactly what we need it to, as we only want linear
>> RGB buffers:
>
> Except in the cases where it doesn't do what you want, and possibly in
> the futu
On Wed, Apr 24, 2013 at 06:52:33PM +0300, ville.syrj...@linux.intel.com wrote:
> Here's the latest version of my plane clipping stuff.
>
> I think it should be ready for merging. Laurent reviewed the first patch,
> and Chris reviewed the whole set.
>
> I didn't hear any bikeshedding about the loc
>> Except in the cases where it doesn't do what you want, and possibly in
>> the future where it does less of what you want. You've started on a
>> slippery slope, and I'm stopping you before you make things worse.
>>
>> You are going to have to get SoC kernel drivers to add an ioctl that
>> you ca
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Tue, Apr 30, 2013 at 10:19 PM, Dave Airlie wrote:
>>> Except in the cases where it doesn't do what you want, and possibly in
>>> the future where it does less of what you want. You've started on a
>>> slippery slope, and I'm stopping you before you make things worse.
>>>
>>> You are going to ha
https://bugs.freedesktop.org/show_bug.cgi?id=60553
Laurent carlier changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=64096
Priority: medium
Bug ID: 64096
Assignee: dri-devel@lists.freedesktop.org
Summary: LLVM RV790 etqw regression since R600: Packetize
instructions
Severity: normal
Classific
https://bugs.freedesktop.org/show_bug.cgi?id=64096
--- Comment #1 from Andy Furniss ---
Testing further some of the mesa demos are also wrong - not that I have re-
bisected, just assume same issue, on heads -
gloss = blank.
gears, fbo_firecube, gearbox = too dark.
shadowtex = shadow misaligned
Hi,
In radeon_atombios.c file, radeon_atombios_parse_power_table_6
function, the power state is selected using the state array index:
power_state = (union pplib_power_state *)&state_array->states[i];
The state array has variable sized states which size should be
computed as said in the atombios.
https://bugs.freedesktop.org/show_bug.cgi?id=64099
Priority: medium
Bug ID: 64099
Assignee: dri-devel@lists.freedesktop.org
Summary: Mesa 9.0.3 implementation error: In
_mesa_DeleteHashTable, found non-freed data
Severity: mi
From: Dave Airlie
Sometimes that extra semicolon can really be hard to spot.
Cc: Imre Deak
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_dmabuf.c
b/drivers/gpu/drm/i915/i
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_reg.h between commit a65851af5938 ("drm/i915:
Make data/link N value power of two") from the drm tree and commit
72419203cab9 ("drm/i915: hw state readout support for fdi m/n") from the
drm-intel tre
Since we ask the dmabuf owner to map the dma-buf into our device
address space, but for udl at present that is the CPU address space,
since we don't DMA directly from the mapped buffer.
However if we don't set a dma mask on the usb device, the mapping
ends up using swiotlb on machines that have it
https://bugzilla.kernel.org/show_bug.cgi?id=47351
Nick changed:
What|Removed |Added
CC||ka.n...@mail.ru
--- Comment #7 from Nick 201
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #4 from Nick 2013-04-30 11:53:07 ---
Created an attachment (id=100301)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100301)
dmesg output
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- Yo
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #5 from Nick 2013-04-30 11:53:33 ---
Created an attachment (id=100311)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100311)
Xorg.0.log
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #29 from Hristo Venev ---
I just noticed a regression: the GPU halts when cold boot was done by fglrx and
driver is switched to radeon.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #6 from Nick 2013-04-30 12:14:25 ---
(In reply to comment #3)
> (In reply to comment #0)
> > After upgrading my AMD E-450-based notebook to a newer one (HP 4545s
> > A4-3300-based) i noticed that in spite of noticeable higher cloc
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #8 from Alex Deucher 2013-04-30 12:57:39
---
(In reply to comment #7)
> Yes, I'm quite sure my laptop is mux-less, so I guess the card actually works
> but cannot output anything...
> I've 1.13.4 installed (and 1.14.1 is availab
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #9 from Nick 2013-04-30 13:18:22 ---
Thank you!
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #7 from Michel Dänzer 2013-04-30 13:32:46 ---
Does not enabling Option "BackingStore" in xorg.conf help?
The high power usage might be due to the discrete GPU being powered on, but the
X server isn't using it, so it doesn't help
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Sun, Apr 28, 2013 at 07:04:07PM +0200, Maarten Lankhorst wrote:
> Changes since RFC patch v1:
> - Updated to use atomic_long instead of atomic, since the reservation_id was
> a long.
> - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
> - removed mutex_locked_set_reservation_i
https://bugs.freedesktop.org/show_bug.cgi?id=59592
--- Comment #10 from n...@detonation.org ---
Sorry for the late reply. Took me some time to get my test setup working after
a distribution upgrade. It seems like your patch does indeed fix the problem.
I've played around with FlightGear for severa
On Mon, Apr 29, 2013 at 12:31 PM, Dave Airlie wrote:
>> The reason we (currently) use the dumb buffer interface is because it
>> does pretty much exactly what we need it to, as we only want linear
>> RGB buffers:
>
> Except in the cases where it doesn't do what you want, and possibly in
> the futu
On Wed, Apr 24, 2013 at 06:52:33PM +0300, ville.syrj...@linux.intel.com wrote:
> Here's the latest version of my plane clipping stuff.
>
> I think it should be ready for merging. Laurent reviewed the first patch,
> and Chris reviewed the whole set.
>
> I didn't hear any bikeshedding about the loc
>> Except in the cases where it doesn't do what you want, and possibly in
>> the future where it does less of what you want. You've started on a
>> slippery slope, and I'm stopping you before you make things worse.
>>
>> You are going to have to get SoC kernel drivers to add an ioctl that
>> you ca
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Tue, Apr 30, 2013 at 10:19 PM, Dave Airlie wrote:
>>> Except in the cases where it doesn't do what you want, and possibly in
>>> the future where it does less of what you want. You've started on a
>>> slippery slope, and I'm stopping you before you make things worse.
>>>
>>> You are going to ha
https://bugs.freedesktop.org/show_bug.cgi?id=60553
Laurent carlier changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=64096
Priority: medium
Bug ID: 64096
Assignee: dri-devel@lists.freedesktop.org
Summary: LLVM RV790 etqw regression since R600: Packetize
instructions
Severity: normal
Classific
https://bugs.freedesktop.org/show_bug.cgi?id=64096
--- Comment #1 from Andy Furniss ---
Testing further some of the mesa demos are also wrong - not that I have re-
bisected, just assume same issue, on heads -
gloss = blank.
gears, fbo_firecube, gearbox = too dark.
shadowtex = shadow misaligned
Hi,
In radeon_atombios.c file, radeon_atombios_parse_power_table_6
function, the power state is selected using the state array index:
power_state = (union pplib_power_state *)&state_array->states[i];
The state array has variable sized states which size should be
computed as said in the atombios.
https://bugs.freedesktop.org/show_bug.cgi?id=64099
Priority: medium
Bug ID: 64099
Assignee: dri-devel@lists.freedesktop.org
Summary: Mesa 9.0.3 implementation error: In
_mesa_DeleteHashTable, found non-freed data
Severity: mi
From: Dave Airlie
Sometimes that extra semicolon can really be hard to spot.
Cc: Imre Deak
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_dmabuf.c
b/drivers/gpu/drm/i915/i
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_reg.h between commit a65851af5938 ("drm/i915:
Make data/link N value power of two") from the drm tree and commit
72419203cab9 ("drm/i915: hw state readout support for fdi m/n") from the
drm-intel tre
Since we ask the dmabuf owner to map the dma-buf into our device
address space, but for udl at present that is the CPU address space,
since we don't DMA directly from the mapped buffer.
However if we don't set a dma mask on the usb device, the mapping
ends up using swiotlb on machines that have it
https://bugzilla.kernel.org/show_bug.cgi?id=47351
Nick changed:
What|Removed |Added
CC||ka.n...@mail.ru
--- Comment #7 from Nick 201
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #4 from Nick 2013-04-30 11:53:07 ---
Created an attachment (id=100301)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100301)
dmesg output
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- Yo
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #5 from Nick 2013-04-30 11:53:33 ---
Created an attachment (id=100311)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100311)
Xorg.0.log
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #29 from Hristo Venev ---
I just noticed a regression: the GPU halts when cold boot was done by fglrx and
driver is switched to radeon.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #6 from Nick 2013-04-30 12:14:25 ---
(In reply to comment #3)
> (In reply to comment #0)
> > After upgrading my AMD E-450-based notebook to a newer one (HP 4545s
> > A4-3300-based) i noticed that in spite of noticeable higher cloc
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #8 from Alex Deucher 2013-04-30 12:57:39
---
(In reply to comment #7)
> Yes, I'm quite sure my laptop is mux-less, so I guess the card actually works
> but cannot output anything...
> I've 1.13.4 installed (and 1.14.1 is availab
https://bugzilla.kernel.org/show_bug.cgi?id=47351
--- Comment #9 from Nick 2013-04-30 13:18:22 ---
Thank you!
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #7 from Michel Dänzer 2013-04-30 13:32:46 ---
Does not enabling Option "BackingStore" in xorg.conf help?
The high power usage might be due to the discrete GPU being powered on, but the
X server isn't using it, so it doesn't help
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Sun, Apr 28, 2013 at 07:04:07PM +0200, Maarten Lankhorst wrote:
> Changes since RFC patch v1:
> - Updated to use atomic_long instead of atomic, since the reservation_id was
> a long.
> - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow
> - removed mutex_locked_set_reservation_i
https://bugs.freedesktop.org/show_bug.cgi?id=59592
--- Comment #10 from n...@detonation.org ---
Sorry for the late reply. Took me some time to get my test setup working after
a distribution upgrade. It seems like your patch does indeed fix the problem.
I've played around with FlightGear for severa
On Mon, Apr 29, 2013 at 12:31 PM, Dave Airlie wrote:
>> The reason we (currently) use the dumb buffer interface is because it
>> does pretty much exactly what we need it to, as we only want linear
>> RGB buffers:
>
> Except in the cases where it doesn't do what you want, and possibly in
> the futu
On Wed, Apr 24, 2013 at 06:52:33PM +0300, ville.syrj...@linux.intel.com wrote:
> Here's the latest version of my plane clipping stuff.
>
> I think it should be ready for merging. Laurent reviewed the first patch,
> and Chris reviewed the whole set.
>
> I didn't hear any bikeshedding about the loc
>> Except in the cases where it doesn't do what you want, and possibly in
>> the future where it does less of what you want. You've started on a
>> slippery slope, and I'm stopping you before you make things worse.
>>
>> You are going to have to get SoC kernel drivers to add an ioctl that
>> you ca
Injects EDEADLK conditions at pseudo-random interval, with exponential
backoff up to UINT_MAX (to ensure that every lock operation still
completes in a reasonable time).
This way we can test the wound slowpath even for ww mutex users where
contention is never expected, and the ww deadlock avoidanc
On Tue, Apr 30, 2013 at 10:19 PM, Dave Airlie wrote:
>>> Except in the cases where it doesn't do what you want, and possibly in
>>> the future where it does less of what you want. You've started on a
>>> slippery slope, and I'm stopping you before you make things worse.
>>>
>>> You are going to ha
https://bugs.freedesktop.org/show_bug.cgi?id=60553
Laurent carlier changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=64096
Priority: medium
Bug ID: 64096
Assignee: dri-devel@lists.freedesktop.org
Summary: LLVM RV790 etqw regression since R600: Packetize
instructions
Severity: normal
Classific
https://bugs.freedesktop.org/show_bug.cgi?id=64096
--- Comment #1 from Andy Furniss ---
Testing further some of the mesa demos are also wrong - not that I have re-
bisected, just assume same issue, on heads -
gloss = blank.
gears, fbo_firecube, gearbox = too dark.
shadowtex = shadow misaligned
Hi,
In radeon_atombios.c file, radeon_atombios_parse_power_table_6
function, the power state is selected using the state array index:
power_state = (union pplib_power_state *)&state_array->states[i];
The state array has variable sized states which size should be
computed as said in the atombios.
https://bugs.freedesktop.org/show_bug.cgi?id=64099
Priority: medium
Bug ID: 64099
Assignee: dri-devel@lists.freedesktop.org
Summary: Mesa 9.0.3 implementation error: In
_mesa_DeleteHashTable, found non-freed data
Severity: mi
From: Dave Airlie
Sometimes that extra semicolon can really be hard to spot.
Cc: Imre Deak
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_gem_dmabuf.c
b/drivers/gpu/drm/i915/i
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_reg.h between commit a65851af5938 ("drm/i915:
Make data/link N value power of two") from the drm tree and commit
72419203cab9 ("drm/i915: hw state readout support for fdi m/n") from the
drm-intel tre
Since we ask the dmabuf owner to map the dma-buf into our device
address space, but for udl at present that is the CPU address space,
since we don't DMA directly from the mapped buffer.
However if we don't set a dma mask on the usb device, the mapping
ends up using swiotlb on machines that have it
https://bugzilla.kernel.org/show_bug.cgi?id=47351
Nick changed:
What|Removed |Added
CC||ka.n...@mail.ru
--- Comment #7 from Nick 201
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #4 from Nick 2013-04-30 11:53:07 ---
Created an attachment (id=100301)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100301)
dmesg output
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- Yo
https://bugzilla.kernel.org/show_bug.cgi?id=57281
--- Comment #5 from Nick 2013-04-30 11:53:33 ---
Created an attachment (id=100311)
--> (https://bugzilla.kernel.org/attachment.cgi?id=100311)
Xorg.0.log
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
--- You
https://bugs.freedesktop.org/show_bug.cgi?id=60879
--- Comment #29 from Hristo Venev ---
I just noticed a regression: the GPU halts when cold boot was done by fglrx and
driver is switched to radeon.
--
You are receiving this mail because:
You are the assignee for the bug.
__
1 - 100 of 144 matches
Mail list logo
