On Die, 2010-04-27 at 12:34 +1000, Dave Airlie wrote:
From: Dave Airlie airl...@redhat.com
On constrained r100 systems compiz would fail to start due to a lack
of memory, we can just fallback place the objects rather than completely
failing it works a lot better.
v2:
fixes issue
https://bugzilla.kernel.org/show_bug.cgi?id=15181
--- Comment #11 from Jérôme Glisse gli...@freedesktop.org 2010-04-27
08:47:15 ---
Please attach drivers/gpu/drm/radeon/radeon_bios.c it seems different from the
one upstream and it's useless to add warn to rom.c.
--
Configure bugmail:
[ Moving to the new list ]
On Die, 2010-04-27 at 12:34 +1000, Dave Airlie wrote:
From: Dave Airlie airl...@redhat.com
On constrained r100 systems compiz would fail to start due to a lack
of memory, we can just fallback place the objects rather than completely
failing it works a lot better.
https://bugzilla.kernel.org/show_bug.cgi?id=15166
--- Comment #38 from Aurélien Couderc zecou...@free.fr 2010-04-27 16:51:41
---
To answer Alex Deucher's questions:
#32 NoAccel doen't solve the problem (driver 6.13.0)
#33 disabling KMS solves the problem and ums+acceleration works fine
--
On Fri, 26 Mar 2010 11:07:19 -0700
Jesse Barnes jbar...@virtuousgeek.org wrote:
On 945, vblank delivery alone seems unreliable. The PIPE*STAT bits get
set correctly, but interrupts occur at a low frequency relative to
refresh. If we enable VSYNC interrupts as well however (even though we
https://bugzilla.kernel.org/show_bug.cgi?id=15166
--- Comment #39 from Alex Deucher alexdeuc...@gmail.com 2010-04-27 17:35:11
---
Created an attachment (id=26161)
-- (https://bugzilla.kernel.org/attachment.cgi?id=26161)
add accel parameter
This patch adds an accel parameter that allows
https://bugzilla.kernel.org/show_bug.cgi?id=15181
--- Comment #12 from Matteo rootki...@yahoo.it 2010-04-27 20:32:37 ---
Created an attachment (id=26165)
-- (https://bugzilla.kernel.org/attachment.cgi?id=26165)
drivers/gpu/drm/radeon/radeon_bios.c
drivers/gpu/drm/radeon/radeon_bios.c
--
From: Dan Carpenter erro...@gmail.com
fx-lock is used as the index in dev_priv-decoder_queue[fx-lock]
which is an array of VIA_NR_XVMC_LOCKS elements.
Signed-off-by: Dan Carpenter erro...@gmail.com
Cc: David Airlie airl...@linux.ie
Signed-off-by: Andrew Morton a...@linux-foundation.org
---
From: Jiri Slaby jsl...@suse.cz
Stanse found that one error path in vga_switcheroo_debugfs_write omits to
unlock vgasr_mutex. Fix that.
Signed-off-by: Jiri Slaby jsl...@suse.cz
Cc: Dave Airlie airl...@redhat.com
Signed-off-by: Andrew Morton a...@linux-foundation.org
---
From: Dan Carpenter erro...@gmail.com
This change makes the array larger, MAX_SUPPORTED_TV_TIMING_V1_2 is 3
and the original size MAX_SUPPORTED_TV_TIMING is 2.
Also there were checks that were off by one.
Signed-off-by: Dan Carpenter erro...@gmail.com
Cc: David Airlie airl...@linux.ie
Acked-by:
From: Dan Carpenter erro...@gmail.com
In the original code we used j as an iterator but we used i as an
index.
- for (j = 0; j i; j++)
- device_remove_file(connector-kdev,
- connector_attrs[i]);
Smatch complained
https://bugzilla.kernel.org/show_bug.cgi?id=15166
--- Comment #40 from Alex Deucher alexdeuc...@gmail.com 2010-04-28 03:38:58
---
I managed to get remote access to an affected machine today, and to start off
with I tried Linus' git tree, bc113f151a73cb2195c2fb40d7d70acf8e2f9208, to be
12 matches
Mail list logo