forked from luck/tmp_suning_uos_patched
7ab876703d
If you'll recall, over a year ago, I pointed out that the current Radeon driver erroneously returns -EINVAL for valid blanking codes, here is a link to that thread: http://lkml.org/lkml/2006/1/28/6 No other driver does this, and it confuses the X server into thinking that the device does not support blanking properly. I looked again and there is simply no reason for the Radeon driver to return -EINVAL for FB_BLANK_NORMAL. It claims it wants to do this in order to convince fbcon to blank in software, right here: if (fb_blank(info, blank)) fbcon_generic_blank(vc, info, blank); to software blank the screen. But it only causes that to happen in the FB_BLANK_NORMAL case. That makes no sense because the Radeon code does this: val |= CRTC_DISPLAY_DIS; in the FB_BLANK_NORMAL case so should be blanking the hardware, and there is therefore no reason to SW blank by returning -EINVAL. Signed-off-by: David S. Miller <davem@davemloft.net> Acked-by: Antonino Daplas <adaplas@gmail.com> |
||
|---|---|---|
| .. | ||
| ati_ids.h | ||
| aty128fb.c | ||
| atyfb_base.c | ||
| atyfb.h | ||
| mach64_accel.c | ||
| mach64_ct.c | ||
| mach64_cursor.c | ||
| mach64_gx.c | ||
| Makefile | ||
| radeon_accel.c | ||
| radeon_backlight.c | ||
| radeon_base.c | ||
| radeon_i2c.c | ||
| radeon_monitor.c | ||
| radeon_pm.c | ||
| radeonfb.h | ||