dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Jani Nikula <jani.nikula@intel.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] i915: failure to interoperate with HP ZR30w using an X230
Date: Sat, 3 Nov 2012 14:07:59 -0400	[thread overview]
Message-ID: <20121103180759.GA5486@thunk.org> (raw)
In-Reply-To: <20121103102158.GP5755@phenom.ffwll.local>

On Sat, Nov 03, 2012 at 11:21:58AM +0100, Daniel Vetter wrote:
> 
> Well, we know for sure that fdi link training is broken - it doesn't match
> at all what the spec says we should do. I've been working on this lately,
> since in quite a few circumstances the link train fails without the
> relevent bits indicating so. While testing I've also noticed that this
> entire thing is highly timing dependent, e.g. denpending upon which
> desktop is running and which tool I use to change the configuration it
> fails or succeeds.

So it is still (somewhat) broken in 3.7-rcX?  Certainly it seems to be
better (at least for me) than what was in 3.6.3.  Or are you saying I
may have just gotten lucky?  :-)

> So I have no suggestions for what could help your system and what should
> get backported, since the current code is still broken.

Thanks for your response and for your work in making the i915 driver
better.  I really appreciate your efforts.

Cheers,

						- Ted

      reply	other threads:[~2012-11-03 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30  0:39 [REGRESSION] i915: failure to interoperate with HP ZR30w using an X230 Theodore Ts'o
2012-10-30  7:44 ` Jani Nikula
2012-10-30 11:57   ` Jani Nikula
2012-10-30 20:32     ` Theodore Ts'o
2012-11-03  0:58       ` Theodore Ts'o
2012-11-03 10:21         ` Daniel Vetter
2012-11-03 18:07           ` Theodore Ts'o [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=20121103180759.GA5486@thunk.org \
    --to=tytso@mit.edu \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).