From: Takashi Iwai <tiwai@suse.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Fix eDP breakages on HP Z1 desktop
Date: Tue, 12 Mar 2013 16:32:26 +0100 [thread overview]
Message-ID: <1363102348-16337-1-git-send-email-tiwai@suse.de> (raw)
Hi,
this is a patch series to fix the breakages of eDP output on HP Z1
desktop machine with IvyBridge since 3.6 kernel.
The first patch is identical as what I already sent yesterday, reverting
a bogus check in the dp train loop. The second one is the patch I cooked
today, for using the correct pixel clock for the fixed eDP panel.
I guess the second patch won't be applied cleanly to the old kernels,
so it'd need to be sent individually to stable kernel if needed.
thanks,
Takashi
next reply other threads:[~2013-03-12 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 15:32 Takashi Iwai [this message]
2013-03-12 15:32 ` [PATCH 1/2] Revert "drm/i915: try to train DP even harder" Takashi Iwai
2013-03-12 15:32 ` [PATCH 2/2] drm/i915: Use the fixed pixel clock for eDP in intel_dp_set_m_n() Takashi Iwai
2013-03-17 22:12 ` Daniel Vetter
2013-03-18 9:29 ` Takashi Iwai
2013-03-18 10:26 ` 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=1363102348-16337-1-git-send-email-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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