From: Thomas Hellstrom <thellstrom@vmware.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: drm-next-misc merge breaks vmwgfx
Date: Thu, 6 Apr 2017 16:56:18 +0200 [thread overview]
Message-ID: <74e20f5a-b3bd-5e9e-9541-2ab1bfdd1345@vmware.com> (raw)
In-Reply-To: <CAKMK7uGwFxcAciPNwrtahkf1vi5xUckvAx7ct01mV=zry-M73w@mail.gmail.com>
On 04/06/2017 04:47 PM, Daniel Vetter wrote:
> On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom <thellstrom@vmware.com> wrote:
>> Also, when testing the tip of drm-misc-next (with the non-atomic vmwgfx)
>> there appeared to be warnings about a non-NULL
>> dev->mode_config.acquire_ctx. I'll see if I can reproduce those, but
>> perhaps removing the line
>>
>> dev->mode_config.acquire_ctx = &ctx
>>
>> in drm_mode_setcrtc()
>>
>> is part of the problem.
> Hm, where do you hit that? And by tip of drm-misc-next, do you mean
> the very latest state, which includes atomic vmwgfx, or is this with
> the non-atomic vmwgfx? Please paste the backtraces (and for which tree
> they are).
> -Daniel
Actually this must have been from a confused rebase-bisect state
somewhere. I can't reproduce this.
/Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-06 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 17:45 drm-next-misc merge breaks vmwgfx Thomas Hellstrom
2017-04-06 12:34 ` Daniel Vetter
2017-04-06 14:10 ` Thomas Hellstrom
2017-04-06 14:46 ` Daniel Vetter
2017-04-06 18:01 ` Thomas Hellstrom
2017-04-06 19:52 ` Daniel Vetter
2017-04-06 14:47 ` Daniel Vetter
2017-04-06 14:56 ` Thomas Hellstrom [this message]
2017-04-06 15:01 ` Daniel Vetter
2017-04-06 15:07 ` Thomas Hellstrom
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=74e20f5a-b3bd-5e9e-9541-2ab1bfdd1345@vmware.com \
--to=thellstrom@vmware.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@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 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.