From: Thomas Richter <thor@math.tu-berlin.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: drm/i915/ns2501: Update from git working
Date: Wed, 09 Oct 2013 07:02:45 +0200 [thread overview]
Message-ID: <5254E375.3020104@math.tu-berlin.de> (raw)
In-Reply-To: <26192_1381269615_5254806F_26192_12488_1_20131008220032.GI8303@phenom.ffwll.local>
On 09.10.2013 00:00, Daniel Vetter wrote:
>
> My drm-intel git branch doesn't yet have the two patches that are meant to
> replace your ns2501 hack ... So I'm not too sure what exactly you've
> tested that made things magically better?
Is there a difference between the 3.12rc4 from kernel.org and the
3.12.rc3+ from your git repository that might explain the difference?
These are the two kernels I tested, with the results as presented.
Kernel.org is apparently one release cycle (and one bug) ahead.
Greetings,
Thomas
next prev parent reply other threads:[~2013-10-09 5:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 10:25 [PATCH 1/3] drm/i915: rip out gen2 reset code Daniel Vetter
2013-10-08 10:25 ` [PATCH 2/3] drm/i915/dvo: call ->mode_set callback only when the port is running Daniel Vetter
2013-10-08 11:31 ` Chris Wilson
2013-10-08 10:25 ` [PATCH 3/3] drm/i915/ns2501: Rip out the reenable hack Daniel Vetter
2013-10-08 10:29 ` [PATCH 1/3] drm/i915: rip out gen2 reset code Chris Wilson
2013-10-08 12:23 ` Daniel Vetter
[not found] ` <26192_1381227964_5253DDBB_26192_8102_1_1381227943-4409-3-git-send-email-daniel.vetter@ffwll.ch>
2013-10-08 20:56 ` drm/i915/ns2501: Update from git working Thomas Richter
2013-10-08 22:00 ` Daniel Vetter
[not found] ` <26192_1381269615_5254806F_26192_12488_1_20131008220032.GI8303@phenom.ffwll.local>
2013-10-09 5:02 ` Thomas Richter [this message]
2013-10-09 7:13 ` Daniel Vetter
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=5254E375.3020104@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox