drm_hwcomposer moving to fd.o

[Tomeu Vizoso]

On 09/25/2017 04:44 AM, Chih-Wei Huang wrote:
> Hey Robert, thank you for the reply.
> 
> 2017-09-22 23:43 GMT+08:00 Robert Foss <robert.foss at collabora.com>:
>> Hey Chih-Wei,
>> On Fri, 2017-09-22 at 10:40 +0800, Chih-Wei Huang wrote:
> 
>> The android-ia project has supported using drm_hwcomposer and an
>> alternative hwcomposer, so it would think there should be no issues.
> 
> By x86 GPUs, I meant i915(i965)/nouveau/radeon/amdgpu/virgl/vmwgfx.
> Among these only virgl works with the current drm_hwcomposer.
> All the others don't have a ready atomic mode-setting API to use it.
> That's the problem which should be addressed I meant.

Most if not all of those drivers support the atomic updates API in
mainline (and have for a few releases by now).

Regards,

Tomeu

> The android-ia doesn't support using fdo's drm_hwcomposer I think.
> They use an alternative hwcomposer [1] as you said.
> It looks very different than drm_hwcomposer though
> both rely on the similar (or same?) atomic API.
> Android-ia's kernel has also been patched to work with it.
> The vanilla kernel (at least LTS 4.9) can't work with [1]
> or drm_hwcomposer.
> Actually [1] only works with i915(i965) but we want
> a more generic hwcomposer like drm_hwcomposer.
> 
> Please correct me if I am wrong.
> 
> 
> [1]: git://github.com/01org/IA-Hardware-Composer
> 
>>> How about the gralloc?
>>> There are also several implementations
>>> scattered somewhere.
>>> I think it's also important to standardize it to fd.o
>>> and make it work with fd.o's drm_hwcomposer.
>>
>> Gralloc is a different story, and the right person to ask about it is
>> not me, but maybe Rob Herring.
> 
> 
>