Re: [PATCH xserver v3 3/3] modesetting: Actually get framebuffer ID

2018-04-05 Thread Adam Jackson
On Thu, 2018-04-05 at 18:01 +0200, Olivier Fourdan wrote: > > On 5 April 2018 at 17:47, Daniel Stone wrote: > > We would fail to get the FB ID if it wasn't already imported, since we > > were checking to see if the pointer was NULL (it never was) rather than > > if the content of the pointer was

Re: [PATCH xserver v3 3/3] modesetting: Actually get framebuffer ID

2018-04-05 Thread Michel Dänzer
On 2018-04-05 05:47 PM, Daniel Stone wrote: > We would fail to get the FB ID if it wasn't already imported, since we > were checking to see if the pointer was NULL (it never was) rather than > if the content of the pointer was 0. > > Signed-off-by: Daniel Stone > Reported-by: Olivier Fourdan > -

Re: [PATCH xserver v3 3/3] modesetting: Actually get framebuffer ID

2018-04-05 Thread Olivier Fourdan
On 5 April 2018 at 17:47, Daniel Stone wrote: > We would fail to get the FB ID if it wasn't already imported, since we > were checking to see if the pointer was NULL (it never was) rather than > if the content of the pointer was 0. > > Signed-off-by: Daniel Stone > Reported-by: Olivier Fourdan

[PATCH xserver v3 3/3] modesetting: Actually get framebuffer ID

2018-04-05 Thread Daniel Stone
We would fail to get the FB ID if it wasn't already imported, since we were checking to see if the pointer was NULL (it never was) rather than if the content of the pointer was 0. Signed-off-by: Daniel Stone Reported-by: Olivier Fourdan --- hw/xfree86/drivers/modesetting/drmmode_display.c | 2 +