http://bugs.freedesktop.org/show_bug.cgi?id=24029
Summary: Compiz water effect causes black screen on r300
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: ASSIGNED
Severity: normal
Pr
Just one comment so far now that I'm using this code.
On Fri, 11 Sep 2009 14:33:34 -0400
"Kristian Høgsberg" wrote:
> + file_priv->event_space -= sizeof e->event;
> + seq = drm_vblank_count(dev, pipe);
> + if ((vblwait->request.type & _DRM_VBLANK_NEXTONMISS) &&
> + (seq - vblw
http://bugs.freedesktop.org/show_bug.cgi?id=23992
--- Comment #3 from Lukasz Krotowski 2009-09-18
11:19:53 PST ---
Created an attachment (id=29671)
--> (http://bugs.freedesktop.org/attachment.cgi?id=29671)
Radeon/DRM part of dmesg.
--
Configure bugmail: http://bugs.freedesktop.org/userp
http://bugs.freedesktop.org/show_bug.cgi?id=23852
--- Comment #2 from Jerome Glisse 2009-09-18 08:34:20
PST ---
Please attach full dmesg of a session with kms one
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: --
>From 3065eb65a36a0b49a7975274b8236fc01127c1db Mon Sep 17 00:00:00 2001
From: Alex Deucher
Date: Fri, 18 Sep 2009 11:30:30 -0400
Subject: [PATCH] drm/radeon/r600/kms: rv670 is not DCE3
RV670 was using the wrong modesetting code.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/radeon.h |
2009/9/17 Rafał Miłecki :
> W dniu 18 września 2009 00:55 użytkownik Rafał Miłecki
> napisał:
>> My new proposition is rather create some "user_power_mode" and let
>> user specify all 3 params. For example:
>> $ echo 20 40 1050 > /sys/class/gpu/user_power_mode
>> $ cat /sys/class/gpu/user_
http://bugs.freedesktop.org/show_bug.cgi?id=23234
--- Comment #13 from Kevin DeKorte 2009-09-18 05:57:13
PST ---
Appears to be fixed using drm-next,drm and ddx (git) from Sep 18, 2009
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this
2009/9/17 Rafał Miłecki
> W dniu 18 września 2009 00:55 użytkownik Rafał Miłecki
> napisał:
> > My new proposition is rather create some "user_power_mode" and let
> > user specify all 3 params. For example:
> > $ echo 20 40 1050 > /sys/class/gpu/user_power_mode
> > $ cat /sys/class/gpu/u
On Fri, 2009-09-18 at 07:45 +0100, Dave Airlie wrote:
> > From: Michel Dänzer
> >
> > Someone on IRC reported problems after commit
> > 95a8f1bf4f48b434c9f839ab5a0773f66b39d7c6 ('drm/radeon/kms: Move
> > radeon_clocks_init() call back after getting VRAM info.'). And indeed, at
> > least
> > som
Dave Airlie writes:
> > An rv350 specific issue then?
>
> I booted it on my desktop rv370 and I'm sure Michel has booted it on
> his rv350 macbook, so might be a bios issue or soemthing else.
Maybe but note that drm-next just complains that there's no modes:
"Connected connector with 0 modes"
>
>
> An rv350 specific issue then?
I booted it on my desktop rv370 and I'm sure Michel has booted it on his
rv350 macbook, so might be a bios issue or soemthing else.
Dave.
--
Come build with us! The BlackBerry® Deve
Thierry Vignaud writes:
> For me, drm-next's still broken even with that patch whereas stock
> 2.6.31 is working fine (modulo hard freeze after a couple hours) on
> RV350 AP [Radeon 9600].
It works fine on RV530 though:
[drm] Initialized drm 1.1.0 20060810
[drm] radeon kernel modesetting enabled
12 matches
Mail list logo
