From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Martin van Es <martin@mrvanes.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge
Date: Thu, 8 Sep 2016 13:18:41 +0300 [thread overview]
Message-ID: <20160908101841.GX4329@intel.com> (raw)
In-Reply-To: <1564110.b7Dt3qjTUK@minivanes>
On Thu, Sep 08, 2016 at 12:04:39PM +0200, Martin van Es wrote:
> On dinsdag 6 september 2016 21:40:48 CEST Ville Syrjälä wrote:
> > On Tue, Sep 06, 2016 at 01:56:20PM +0300, Ville Syrjälä wrote:
> > > Actually I just cooked up another branch [2]. It just throws in some
> > > memory barriers to the opregion code, and adds a a new debug print so
> > > to show the response from the BIOS. I'm not too optimistic that the
> > > memory barriers would fix it, but at least we'd get to see the full
> > > response from the BIOS. Can you give this a try?
> > >
> > > [2] git://github.com/vsyrjala/linux.git opregion_panel_type_stuff
>
> This kernel doesn't boot (for me).
>
> I cloned the repo, copied .config from 4.7 kernel, make oldconfig, accepted
> all defaults and made+installed the kernel. This installed an image 4.0.0-rc7+
> (is that correct?) that was unbootable (halts at loading ramdisk).
The version should be 4.7 or 4.8 something. Maybe you used the wrong
branch?
Anywyas I pushed a new branch "opregion_panel_type_quirk" which I'm
hoping will be the final fix we go with. Just waiting for confirmation
that I got the quirk right and that the original machine fixed by the
OpRegion stuff still works. You might want to test that one as well.
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-08 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 15:28 [PATCH 0/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge Andrea Arcangeli
2016-08-28 15:28 ` [PATCH 1/1] " Andrea Arcangeli
2016-08-29 7:24 ` Jani Nikula
2016-08-29 13:32 ` Andrea Arcangeli
2016-08-29 15:08 ` Jani Nikula
2016-08-29 18:48 ` Andrea Arcangeli
2016-08-30 6:54 ` Martin van Es
2016-08-30 8:13 ` Jani Nikula
2016-08-30 9:13 ` Martin van Es
2016-08-30 7:25 ` Jani Nikula
2016-09-06 9:20 ` Ville Syrjälä
2016-09-06 10:56 ` Ville Syrjälä
2016-09-06 18:40 ` Ville Syrjälä
2016-09-08 10:04 ` Martin van Es
2016-09-08 10:18 ` Ville Syrjälä [this message]
2016-09-08 11:09 ` Martin van Es
2016-09-08 13:53 ` Andrea Arcangeli
2016-09-14 9:40 ` [PATCH 0/1] " 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=20160908101841.GX4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=martin@mrvanes.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 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.