From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Joep Daandels <jdaandels@home.nl>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: please revert 869184a675662bddcdf76c5b95665272facff2b8 ASAP
Date: Thu, 9 Dec 2010 13:04:55 -0800 [thread overview]
Message-ID: <20101209130455.2717c50a@jbarnes-desktop> (raw)
In-Reply-To: <loom.20101209T205908-457@post.gmane.org>
On Thu, 9 Dec 2010 20:05:44 +0000 (UTC)
Joep Daandels <jdaandels@home.nl> wrote:
> Chris Wilson <chris <at> chris-wilson.co.uk> writes:
>
> >
> > On Mon, 29 Nov 2010 20:06:23 +1000, Dave Airlie <airlied <at> gmail.com> wrote:
> > > drm/i915/dp: use VBT provided eDP params if available
> > >
> > > Looks like trusting the BIOS is a bad plan, also that commit seems to
> > > do a lot more than just use some VBT values, probably needs more
> > > splitting up from jbarnes.
> >
> > I've had one lucky Vaio owner report that this revert breaks his machine.
> > Looks like a partial revert is in order. eDP, what fun.
> > -Chris
> >
>
>
> I'm afraid he's not the only vaio owner with problems. I was quite happy with
> 2.6.37 rc 2 to 4 because finally the display port was detected again after
> skipping 2.6.36 because of the issue.
>
> Only just found this thread with an explaination why I was unable to work 2.6.36.
>
> Is there any chance eDP will work again in the final release without breaking
> other laptops:
Possible but unlikely. I'm still waiting to receive a couple more
laptops for testing so I can fix all of them at once rather than fixing
one and breaking another...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-12-09 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 10:06 please revert 869184a675662bddcdf76c5b95665272facff2b8 ASAP Dave Airlie
2010-11-29 19:14 ` Chris Wilson
2010-11-29 20:19 ` Dave Airlie
2010-11-30 9:29 ` Chris Wilson
2010-12-09 20:05 ` Joep Daandels
2010-12-09 21:04 ` Jesse Barnes [this message]
2010-12-06 18:04 ` Jesse Barnes
2010-12-06 22:32 ` Dave Airlie
2010-12-06 22:35 ` 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=20101209130455.2717c50a@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jdaandels@home.nl \
/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