On Thu, Apr 6, 2017 at 8:01 PM, Thomas Hellstrom wrote:
> On 04/06/2017 04:46 PM, Daniel Vetter wrote:
>> On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom
>> wrote:
>>> On 04/06/2017 02:34 PM, Daniel Vetter wrote:
Hi Thomas,
Bisected
On 04/06/2017 04:46 PM, Daniel Vetter wrote:
> On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom
> wrote:
>> On 04/06/2017 02:34 PM, Daniel Vetter wrote:
>>> Hi Thomas,
>>>
>>> Bisected an offender already? Afaik there's no one else who reported
>>> issues thus far, and for
On 04/06/2017 05:01 PM, Daniel Vetter wrote:
> On Thu, Apr 6, 2017 at 4:56 PM, Thomas Hellstrom
> wrote:
>> On 04/06/2017 04:47 PM, Daniel Vetter wrote:
>>> On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom
>>> wrote:
Also, when testing the tip
On Thu, Apr 6, 2017 at 4:56 PM, Thomas Hellstrom wrote:
> On 04/06/2017 04:47 PM, Daniel Vetter wrote:
>> On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom
>> wrote:
>>> Also, when testing the tip of drm-misc-next (with the non-atomic vmwgfx)
>>>
On 04/06/2017 04:47 PM, Daniel Vetter wrote:
> On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom
> 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
On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom 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
On Thu, Apr 6, 2017 at 4:10 PM, Thomas Hellstrom wrote:
> On 04/06/2017 02:34 PM, Daniel Vetter wrote:
>> Hi Thomas,
>>
>> Bisected an offender already? Afaik there's no one else who reported
>> issues thus far, and for our own CI it seems all still fine.
>> -Daniel
>
> Hi,
On 04/06/2017 02:34 PM, Daniel Vetter wrote:
> Hi Thomas,
>
> Bisected an offender already? Afaik there's no one else who reported
> issues thus far, and for our own CI it seems all still fine.
> -Daniel
Hi, Daniel,
Yes, I rebased drm-misc-next on top of vmwgfx-next and found the culprit
to be
Hi Thomas,
Bisected an offender already? Afaik there's no one else who reported
issues thus far, and for our own CI it seems all still fine.
-Daniel
On Wed, Apr 5, 2017 at 7:45 PM, Thomas Hellstrom wrote:
> Hi!
>
> It appears like the drm-next commit 320d8c3d3 "Merge tag
Hi!
It appears like the drm-next commit 320d8c3d3 "Merge tag
'drm-misc-next-2017-03-31..." breaks vmwgfx.
A black screen shown where plymouthd use to show the boot splash on
Fedora 25. Nothing relevant in the logs.
I eyed through the vmwgfx conflict fixes, but nothing immediately stands
out as
10 matches
Mail list logo