On Sat, Mar 31, 2012 at 6:58 PM, Linus Torvalds
<torvalds(a)linux-foundation.org> wrote:
> - drm dma-buf prime support. Dave Airlie sent me the pull request but
> didn't push very hard for it, it's in my "ok, I can still pull it for
> 3.4 if individual DRM driver people tell me that it will make their
> lives easier." So this is in limbo - I have nothing against it, but I
> won't pull unless I get a few people say "yes, please".
yes, please :-)
Note that the core …
[View More]drm dma-buf/prime support has already been reviewed
by a lot of folks, and tested with a few different drivers (exynos,
omapdrm, i915, nouveau, udl) with some driver support that could be
pushed for 3.5 cycle if the core support makes it in for 3.4 cycle.
BR,
-R
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=27184
--- Comment #26 from Alex Deucher <agd5f(a)yahoo.com> 2012-04-04 06:07:48 PDT ---
(In reply to comment #25)
> I just happened to test with this very same 3.3.0-rc3 kernel that while I was
> in linux console ie. no X and the screen blanker got activated, the lcd display
> was put into suspend mode ---> I hit the keyboard at this stage and the screen
> came back without fuss. Last time when I tried all the different stages …
[View More]with
> xset, none of them worked well. Is there an easy way to modify the states the
> console screen saver is using (for testing purposes) ?
You can use xset to test dpms, e.g.,
xset dpms force off
Also, for what it's worth, the driver only implements two states: on and off.
All of the intermediate dpms states that are not "on" map to "off".
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=27184
--- Comment #25 from tomi.orava(a)ncircle.nullnet.fi 2012-04-04 04:39:41 PDT ---
I just happened to test with this very same 3.3.0-rc3 kernel that while I was
in linux console ie. no X and the screen blanker got activated, the lcd display
was put into suspend mode ---> I hit the keyboard at this stage and the screen
came back without fuss. Last time when I tried all the different stages with
xset, none of them worked well. Is there an easy …
[View More]way to modify the states the
console screen saver is using (for testing purposes) ?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
From: Alex Deucher <alexander.deucher(a)amd.com>
Some r4xx chips have the wrong frev in the
DVOEncoderControl table. It should always be 1
on r4xx. Fixes modesetting on DVO on r4xx chips
with the bad frev.
Reported by twied on #radeon.
Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com>
Cc: stable(a)vger.kernel.org
---
drivers/gpu/drm/radeon/atombios_encoders.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/…
[View More]atombios_encoders.c b/drivers/gpu/drm/radeon/atombios_encoders.c
index b88c460..5e1d0b5 100644
--- a/drivers/gpu/drm/radeon/atombios_encoders.c
+++ b/drivers/gpu/drm/radeon/atombios_encoders.c
@@ -230,6 +230,10 @@ atombios_dvo_setup(struct drm_encoder *encoder, int action)
if (!atom_parse_cmd_header(rdev->mode_info.atom_context, index, &frev, &crev))
return;
+ /* some R4xx chips have the wrong frev */
+ if (rdev->family <= CHIP_RV410)
+ frev = 1;
+
switch (frev) {
case 1:
switch (crev) {
--
1.7.7.5
[View Less]