From: "Sun, Yi" <yi.sun@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: "Yang, Guang A" <guang.a.yang@intel.com>
Subject: Re: Updated -next
Date: Thu, 29 Mar 2012 07:38:15 +0000 [thread overview]
Message-ID: <D9F66AA509623343B6A9A3D4502D5A520FCDC383@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <20120323100310.GB4087@phenom.ffwll.local>
Hi all,
We finished new round Kernel testing. We covered both mobile and desktop machines on platforms IVB, SNB, ILK, GM965 and PNV.
The Kernel the latest on -testing branch Daniel's tree:
commit 0028cac2e9e91961384ac15aae4196eee0faf4f6
Merge: 121d527 b250da7
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Fri Mar 23 10:44:16 2012 +0100
Merge remote-tracking branch 'keithp-kernel/drm-intel-fixes' into drm-intel-testing
Conflicts: drivers/gpu/drm/i915/intel_ringbuffer.c
No new bugs are filed during this circle.
But some old bugs about 3 pipes or eDP on IVB platform are still open now:
Bug 41976 - [IVB] screen turn to be black while switching between console and x-window with 3-pipe active. (https://bugs.freedesktop.org/show_bug.cgi?id=41976)
Bug 42194 - [IVB/SNB]plug in a monitor while running testdisplay fail to make the screen come up. (https://bugs.freedesktop.org/show_bug.cgi?id=42194)
Bug 44309 - [IVB eDP] 3 pipe doesn't work with eDP monitor. (https://bugs.freedesktop.org/show_bug.cgi?id=44309)
Bug 45867 - [IVB 3pipe] 3 Pipe Doesn't Work with Eaglemont Card. (https://bugs.freedesktop.org/show_bug.cgi?id=45867)
Thanks
--Yi,Sun
> -----Original Message-----
> From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Friday, March 23, 2012 6:03 PM
> To: Intel Graphics Development; Sun, Yi
> Subject: Updated -next
>
> Hi all,
>
> I've pushed out an updated -next and -testing tree. Highlights:
> - more decoupling of ppgtt and global gtt.
> - shut up the compiler (Ben)
> - a bunch of minor quirks and fixlets, accompanied with quite a few module
> options to ease debuggin (and adding new entries to these for these new
> quirks).
>
> This -next tree is already targeting 3.5.
>
> Happy testing!
> -Daniel
> --
> Daniel Vetter
> Mail: daniel@ffwll.ch
> Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-03-29 7:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 10:03 Updated -next Daniel Vetter
2012-03-29 7:38 ` Sun, Yi [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-22 14:33 updated -next Daniel Vetter
2012-06-21 8:25 Updated -next Daniel Vetter
2012-06-04 20:59 Daniel Vetter
2012-06-12 8:37 ` Daniel Vetter
2012-05-06 19:09 Daniel Vetter
2012-04-21 16:40 Daniel Vetter
2012-04-23 7:39 ` Daniel Vetter
2012-04-23 7:40 ` Sun, Yi
2012-04-27 11:45 ` Daniel Vetter
2012-04-27 13:44 ` Daniel Vetter
2012-04-05 9:45 Daniel Vetter
2012-04-09 16:19 ` Daniel Vetter
2012-04-10 2:09 ` Sun, Yi
2012-04-11 3:20 ` Sun, Yi
2012-04-11 7:54 ` Paul Menzel
2012-04-11 8:24 ` Sun, Yi
2012-04-11 9:45 ` Paul Menzel
2012-03-01 20:59 Daniel Vetter
2012-03-08 8:10 ` Sun, Yi
2012-03-18 21:20 ` Daniel Vetter
2012-02-16 17:27 updated -next Daniel Vetter
2012-02-17 17:56 ` Jesse Barnes
2012-02-21 7:45 ` Sun, Yi
2012-02-07 22:59 Daniel Vetter
2012-01-20 10:10 Updated -next Daniel Vetter
2012-01-21 4:15 ` Sun, Yi
2012-01-21 14:12 ` Daniel Vetter
2012-01-21 19:45 ` Alan W. Irwin
2012-01-31 9:07 ` Jin, Gordon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9F66AA509623343B6A9A3D4502D5A520FCDC383@SHSMSX102.ccr.corp.intel.com \
--to=yi.sun@intel.com \
--cc=daniel@ffwll.ch \
--cc=guang.a.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.