From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Paul Menzel <paulepanter@users.sourceforge.net>,
Dave Airlie <airlied@gmail.com>, Adam Jackson <ajax@redhat.com>
Cc: Florian Mickler <florian@mickler.org>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] Revert "drm: Add EDID_QUIRK_FORCE_REDUCED_BLANKING for ASUS VW222S"
Date: Wed, 13 Feb 2013 12:05:00 +0200 [thread overview]
Message-ID: <87a9r8r0kz.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uEqDwSToe4EjaXRTX1gqyWcqndLzYpsoFfArtUxVYXctw@mail.gmail.com>
On Tue, 29 Jan 2013, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> On Mon, Jan 14, 2013 at 3:37 PM, Paul Menzel
> <paulepanter@users.sourceforge.net> wrote:
>> Am Montag, den 14.01.2013, 11:06 +0100 schrieb Daniel Vetter:
>>> This reverts commit 6f33814bd4d9cfe76033a31b1c0c76c960cd8e4b.
>>>
>>> The quirk cause a regression, and it looks like the original bug was
>>> simply a lack of FIFO bandwidth on the i915G of the reporter. Which
>>> should eventually be fixed as soon as we get around to implemented
>>> DSPARB FIFO reassignment on gen 3.
>>
>> Reported-by: Florian Mickler <florian@mickler.org>
>>
>>> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=52281
>>> Cc: stable@vger.kernel.org
>>> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>
>
> Hm, revert hasn't landed anywhere yet :( Dave, Ajax: ping?
100% packet loss... another ping.
BR,
Jani.
prev parent reply other threads:[~2013-02-13 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 10:06 [PATCH] Revert "drm: Add EDID_QUIRK_FORCE_REDUCED_BLANKING for ASUS VW222S" Daniel Vetter
2013-01-14 14:37 ` Paul Menzel
2013-01-29 14:13 ` Daniel Vetter
2013-02-13 10:05 ` Jani Nikula [this message]
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=87a9r8r0kz.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=ajax@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=florian@mickler.org \
--cc=paulepanter@users.sourceforge.net \
--cc=stable@vger.kernel.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