From: Jani Nikula <jani.nikula@linux.intel.com>
To: Knut Petersen <Knut_Petersen@t-online.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Use the first mode if there is no preferred mode in the EDID
Date: Thu, 15 May 2014 11:13:01 +0300 [thread overview]
Message-ID: <87k39npiia.fsf@intel.com> (raw)
In-Reply-To: <5373009B.50800@t-online.de>
On Wed, 14 May 2014, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> On 13.05.2014 22:24, Jesse Barnes wrote:
>> On Tue, 13 May 2014 16:50:12 +0100
>> Chris Wilson <chris@chris-wilson.co.uk> wrote:
>>
>>> On Tue, May 13, 2014 at 04:07:37PM +0100, Chris Wilson wrote:
>>>> This matches the algorithm used by earlier kernels when selecting the
>>>> mode for the fbcon. And only if there is no modes at all, do we fall
>>>> back to using the BIOS configuration. Seamless transition is still
>>>> preserved (from the BIOS configuration to ours) so long as the BIOS has
>>>> also chosen what we hope is the native configuration.
>>>>
>>>> Reported-by: Knut Petersen <Knut_Petersen@t-online.de>
>>>> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=78655
>>>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>>>> Cc: stable@vger.kernel.org
> I don't think that Cc: stable@vger.kernel.org is necessary, kernels up
> to 3.14.x don't expose the problem. And as this fixes a post-3.14
> regression this is a clear candidate for 3.15
Chris, do we drop cc: stable?
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-05-15 8:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 15:07 [PATCH] drm/i915: Use the first mode if there is no preferred mode in the EDID Chris Wilson
2014-05-13 15:50 ` Chris Wilson
2014-05-13 20:24 ` Jesse Barnes
2014-05-14 5:35 ` Knut Petersen
2014-05-15 8:13 ` Jani Nikula [this message]
2014-05-15 8:19 ` Chris Wilson
2014-05-19 17:20 ` Knut Petersen
2014-05-19 21:58 ` Daniel Vetter
2014-05-15 8:57 ` Jani Nikula
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=87k39npiia.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Knut_Petersen@t-online.de \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--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 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.