public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Cristian Rodríguez" <crrodriguez@opensuse.org>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: display problems since: drm/i915/dp: workaround BIOS eDP bpp clamping issue
Date: Mon, 4 Nov 2013 22:08:03 +0200	[thread overview]
Message-ID: <20131104200803.GW13047@intel.com> (raw)
In-Reply-To: <5277F66A.8090200@opensuse.org>

On Mon, Nov 04, 2013 at 07:32:58PM +0000, Cristian Rodríguez wrote:
> El 04/11/13 18:54, Cristian Rodríguez escribió:
> > El 04/11/13 18:40, Daniel Vetter escribió:
> >
> >> It hangs on a scanline wait. Are you already on the latest version of
> >> xfree86-video-intel and if not can you please check whether it works
> >> on the latest?
> >
> > I am in version 2.99.905 , it does not appear to be a  newer snapshot
> > release.. do you want me to try a git HEAD version instead ?
> >
> >
> >
> Ok, upgraded the userspace driver to current git HEAD (last commit 4 
> hours ago) attached is the latest errors.

0x01870000:      0x11000001: MI_LOAD_REGISTER_IMM
0x01870004:      0x00044050:    dword 1
0x01870008:      0xfffffeff:    dword 2
0x0187000c:      0x11000001: MI_LOAD_REGISTER_IMM
0x01870010:      0x0004f100:    dword 1
0x01870014:      0xe0500410:    dword 2
0x01870018:      0x01800100: MI_WAIT_FOR_EVENT, plane B scan line wait
0x0187001c:      0x11000001: MI_LOAD_REGISTER_IMM
0x01870020:      0x00044050:    dword 1
0x01870024:      0xffffffff:    dword 2

BSpec says LRIs targeting display engine register should be followed
by SRMs. Looks like the ddx doesn't follow that rule. Not sure it
has anything to do with the problem though.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-11-04 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5273D6EA.7040905@opensuse.org>
2013-11-01 18:45 ` display problems since: drm/i915/dp: workaround BIOS eDP bpp clamping issue Daniel Vetter
2013-11-01 20:02   ` Cristian Rodríguez
2013-11-01 20:20     ` Daniel Vetter
2013-11-01 21:04       ` Cristian Rodríguez
2013-11-01 22:18         ` Daniel Vetter
2013-11-01 23:03           ` Cristian Rodríguez
2013-11-04 15:30           ` Cristian Rodríguez
2013-11-04 18:30             ` Cristian Rodríguez
2013-11-04 18:40               ` Daniel Vetter
2013-11-04 18:54                 ` Cristian Rodríguez
2013-11-04 19:32                   ` Cristian Rodríguez
2013-11-04 20:08                     ` Ville Syrjälä [this message]
2013-11-05  7:59     ` 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=20131104200803.GW13047@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=crrodriguez@opensuse.org \
    --cc=intel-gfx@lists.freedesktop.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