Re: regression on Carrizo display bringup

2017-11-14 Thread Michel Dänzer
On 14/11/17 03:37 PM, Tom St Denis wrote: > On 14/11/17 09:36 AM, Harry Wentland wrote: >> On 2017-11-14 08:30 AM, Tom St Denis wrote: >>> Hi all, >>> >>> Found when testing the tip of drm-next on my A12-9800 Carrizo. >>> >>> [root@carrizo linux]# git bisect good >>>

Re: regression on Carrizo display bringup

2017-11-14 Thread Harry Wentland
On 2017-11-14 08:30 AM, Tom St Denis wrote: > Hi all, > > Found when testing the tip of drm-next on my A12-9800 Carrizo. > > [root@carrizo linux]# git bisect good > 138a3358c17918bb5cd5aa1ea9e8760ac69c515d is the first bad commit > commit 138a3358c17918bb5cd5aa1ea9e8760ac69c515d > Author:

Re: regression on Carrizo display bringup

2017-11-14 Thread Tom St Denis
On 14/11/17 09:36 AM, Harry Wentland wrote: On 2017-11-14 08:30 AM, Tom St Denis wrote: Hi all, Found when testing the tip of drm-next on my A12-9800 Carrizo. [root@carrizo linux]# git bisect good 138a3358c17918bb5cd5aa1ea9e8760ac69c515d is the first bad commit commit

regression on Carrizo display bringup

2017-11-14 Thread Tom St Denis
Hi all, Found when testing the tip of drm-next on my A12-9800 Carrizo. [root@carrizo linux]# git bisect good 138a3358c17918bb5cd5aa1ea9e8760ac69c515d is the first bad commit commit 138a3358c17918bb5cd5aa1ea9e8760ac69c515d Author: Yongqiang Sun Date: Tue Nov 7 11:01:34