Hardware 3D acceleration doesn't work anymore with the latest git kernel

From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Ilia Mirkin <imirkin@alum.mit.edu>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Hardware 3D acceleration doesn't work anymore with the latest git kernel
Date: Wed, 22 Nov 2017 14:40:04 +0100	[thread overview]
Message-ID: <e3d50399-47ca-f90d-f039-dc5c71f3d056@xenosoft.de> (raw)
In-Reply-To: <CAKb7Uvi=LvD6Us+mgs5neSM=z1Ffskrtj28T-XnY5MjsdErWGg@mail.gmail.com>

On 22 November 2017 at 2:27PM, Ilia Mirkin wrote:
> On Wed, Nov 22, 2017 at 8:20 AM, Christian Zigotzky
> <chzigotzky@xenosoft.de> wrote:
>> Hi Alex,
>>
>> I reverted the following files in the first bad commit (first DRM updates)
> Is the merge commit really the first bad commit? i.e. both parents of
> the merge are good, but the merge commit itself is bad? Or did you do
> this manually and therefore didn't go into the merge parents? If so,
> I'd recommend doing a proper bisect (search for "git bisect", there
> are tons of guides). That will identify the commit that's actually
> responsible.
>
> Cheers,
>
>    -ilia
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

Hi ilia,

I did it manually. If I revert the merge commit then the hardware 3D 
acceleration works. Is it possible to bisect in the merge commit directly?

Thanks,
Christian

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel