Signed-off-by: Bruno Prémont bonb...@linux-vserver.org
---
drivers/acpi/video.c|2 +-
drivers/gpu/drm/nouveau/nouveau_backlight.c |4 ++--
drivers/macintosh/via-pmu-backlight.c |4 ++--
drivers/platform/x86/acer-wmi.c |2
() check.
Signed-off-by: Bruno Prémont bonb...@linux-vserver.org
--
Hi Eric, Ma Ling,
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0c2e39525b3b53a97a0202c5f35058147e53977e
(drm/i915: Add support for dual-channel LVDS on 8xx.) is not sufficient
for i8xx, below patch
() check.
Signed-off-by: Bruno Prémont bonb...@linux-vserver.org
--
Hi Eric, Ma Ling,
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=0c2e39525b3b53a97a0202c5f35058147e53977e
(drm/i915: Add support for dual-channel LVDS on 8xx.) is not sufficient
for i8xx, below patch
With KMS working as of comment #50 bug 20115 (KMS fails to completely
configure 855 chip) http://bugs.freedesktop.org/show_bug.cgi?id=20115
I end up with:
[0.537796] [drm] Initialized drm 1.1.0 20060810
[0.537892] i915 :00:02.0: power state changed by ACPI to D0
[0.538218] ACPI:
. The selects for FB_CFB_* do
not cause their dependency FB to get selected as well.
Signed-off-by: Bruno Prémont bonb...@linux-vserver.org
Reported-by: Alec Ari neotheu...@ymail.com
---
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index a74980b..f0c5943 100644
--- a/drivers/gpu/drm
On Sat, 28 February 2009 Eric Anholt e...@anholt.net wrote:
On Sat, 2009-02-28 at 00:47 -0800, Andrew Morton wrote:
The kernel deadlocked on struct_mutex, did it not? That's a kernel
bug regardless of what userspace you're running.
Do we know why this happened?
Userland went stomping
This patch does not work for me.
With this patch applied kernel fails to read EDID data and discover
proper modes. (It ends up displaying a picture looking like the BIOS
bootup image). X fails to start finding no valid mode for LVDS output.
Without the patch Xorg doesn't start either, being
When booting into VGA console and executing the following command sequence I
end up with the trace below (which seems to imply that unichrome DRM driver
[via] and viafb enter a race for some memory resource or disagree on the state
of the chipset after unloading).
This looks like the race happens
On Sat, 19 July 2008 nagaraj s k [EMAIL PROTECTED] wrote:
Hi ALL,
Sorry about repetitive mails, i forgot to add the main mail list,
getting used to the procedure to send patches.
This is my second submission (looks like first mail lost in the
malling list 10 days earlier). I did my best
