From: Daniel Vetter <daniel.vetter@intel.com>
To: dedekind1@gmail.com, "Barnes, Jesse" <jesse.barnes@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: v3.12 does not work on ByT-I
Date: Thu, 07 Nov 2013 13:30:34 +0100 [thread overview]
Message-ID: <527B87EA.4060800@intel.com> (raw)
In-Reply-To: <1383827000.2722.216.camel@sauron.fi.intel.com>
On 07/11/2013 13:23, Artem Bityutskiy wrote:
> Anyway, I've bisected it, and found out that this commit fixes our
> problem:
>
> 0b6279520519 drm/i915/vlv: re-enable hotplug detect based probing on VLV/BYT
>
> Jesse, Daniel, any idea what is the issue and why this patch fixes it?
> The thing is that Tizen IVI boots to UI just fine with 3.12 plus this
> patch, while stock 3.12 does not work.
>
> We also have this bug-report about the problem:
> https://bugs.tizen.org/jira/browse/TIVI-2085
>
> Are OK sending this patch to GregKH / stable for 3.12.x inclusion?
Sure (although the drm-next tree hasn't been merged yet into Linus'
tree). When you send the mail to greg please alos include
533df0fecded drm/i915: vlv: fix VGA hotplug after modeset
in your stable backport request, it's the 2nd half of the fix.
-Daniel
Intel Semiconductor AG
Registered No. 020.30.913.786-7
Registered Office: World Trade Center, Leutschenbachstrasse 95, 8050 Zurich, Switzerland
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2013-11-07 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 12:23 v3.12 does not work on ByT-I Artem Bityutskiy
2013-11-07 12:30 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 12:21 Bityutskiy, Artem
2013-11-07 16:04 ` Jesse Barnes
2013-11-08 14:53 ` Artem Bityutskiy
2013-11-08 18:38 ` Jesse Barnes
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=527B87EA.4060800@intel.com \
--to=daniel.vetter@intel.com \
--cc=dedekind1@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
/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