how get drm-intel-next into a stable kernel
Hi, Have some kind of howto doc ?, about merging, testing os using drm-intel-next with a stable kernel, lets say kernel-2.6.35.
Thanks,
Signature · 1 line
Sérgio M. B.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 2 lines · On Thu, 05 Aug 2010 16:38:55 +0100 Sergio Monteiro Basto…
Hi, Have some kind of howto doc ?, about merging, testing os using drm-intel-next with a stable kernel, lets say kernel-2.6.35.
Short answer: you don't. The drm-intel-next branch is a full kernel tree by itself, and I wouldn't recommend copying files from a drm-intel-next checkout into a stable kernel.
Longer answer: drm-intel-next bits are targeted at the next kernel release. When important fixes from drm-intel-next land in Linus's tree, you can request that they be back ported to the stable tree by sending a note to [email protected] with the commit id(s). They have to meet the stable criteria though; I think the kernel has a doc on what makes something eligible for stable inclusion.
Signature · 1 line
Jesse Barnes, Intel Open Source Technology Center
Quoted 6 lines · Jesse Barnes
Longer answer: drm-intel-next bits are targeted at the next kernel release. When important fixes from drm-intel-next land in Linus's tree, you can request that they be back ported to the stable tree by sending a note to [email protected] with the commit id(s). They have to meet the stable criteria though; I think the kernel has a doc on what makes something eligible for stable inclusion.
Yes we do, see the file, Documenation/stable_kernel_rules.txt
thanks,
greg k-h
Any suggestions of patches to test for those of us still experiencing eDP problems? I've seen a bunch fly by the list, but it's been unclear to me which were supposed to address what issues, or how successful any of them were.
I was able to get 2.6.34 to work on my Dell E6510 by reverting 885a5fb5b120a5c7e0b3baad7b0feb5a89f76c18 as suggested in http://lists.freedesktop.org/archives/intel-gfx/2010-May/006948.html
This no longer works on 2.6.35 (black screen after starting X).
Even with that patch reverted on 2.6.34, I still ran into problems after suspend: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/596080
I can hibernate as a work-around, but that often takes several minutes.
Quoted 1 line · Timothy B. Terriberry
This no longer works on 2.6.35 (black screen after starting X).
Could be https://bugzilla.kernel.org/show_bug.cgi?id=16496 ?
Brice
Quoted 4 lines · Brice Goglin
Quoted 1 line · Timothy B. Terriberry
This no longer works on 2.6.35 (black screen after starting X).
Could be https://bugzilla.kernel.org/show_bug.cgi?id=16496 ?
Reverting that patch (or, more accurately, just deleting the redundant backlight_off call) does indeed solve the problem when initially starting X. So now it's just the suspend issue. Same behavior as 2.6.34: when resuming, the display is off, and switching VTs, etc., won't turn it on. What does work, if I type very carefully, is hibernating and then resuming.
Quoted 6 lines · Timothy B. Terriberry
So now it's just the suspend issue. Same behavior as 2.6.34:
when resuming, the display is off, and switching VTs, etc., won't turn
it on. What does work, if I type very carefully, is hibernating and then
resuming.
Suspend just supposed to work with drm-intel-next and is not (yet) in stables kernel.
As workaround (a good one). I boot with option acpi_sleep=s3_bios, and remove /usr/lib64/pm-utils/sleep.d/99video .
which works very well with my E6410.
Signature · 1 line
Sérgio M. B.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx