[Mesa-dev] [android-x86-devel] Re: About drm_hwcomposer (Was Re: About the PixelFormat mappings in drm_gralloc)

[Rob Herring]

On Wed, Feb 3, 2016 at 10:16 AM, Sean Paul <seanpaul at chromium.org> wrote:
>
>
> On Thu, Jan 21, 2016 at 10:00 AM, Sean Paul <seanpaul at chromium.org> wrote:
>>
>>
>>
>> On Wed, Jan 20, 2016 at 8:49 PM, Chih-Wei Huang <cwhuang at android-x86.org>
>> wrote:
>>>
>>> CC to the android-x86 devel list so more developers can follow.
>>>
>>> 2016-01-21 6:19 GMT+08:00 Rob Clark <robdclark at gmail.com>:
>>> > On Wed, Jan 20, 2016 at 4:59 PM, Rob Herring <robh at kernel.org> wrote:
>>> >> Hi Sean,
>>> >>
>>> >> On Thu, Jan 14, 2016 at 1:15 PM, Sean Paul <seanpaul at chromium.org>
>>> >> wrote:
>>> >>>
>>> >>>
>>> >>> On Thu, Jan 14, 2016 at 9:47 AM, Chih-Wei Huang
>>> >>> <cwhuang at android-x86.org>
>>> >>> wrote:
>>> >>>>
>>> >>>> Hello Sean,
>>> >>>> My last try of drm_hwcomposer failed due to
>>> >>>> my limited time and knowledge.
>>> >>>>
>>> >>>> Fortunately more developers join us
>>> >>>> to work on this topic now, including
>>> >>>> Rob Herring (kernel drm developer),
>>> >>>> Rob Clark and Emil Velikov (Mesa developers)
>>> >>>> We are working on drm_hwcomposer
>>> >>>> for virtio-gpu, the emulated GPU for QEMU.
>>> >>>>
>>> >>>> If you don't mind, I would invite you to join
>>> >>>> our devel group for the discussion.
>>> >>>
>>> >>>
>>> >>> [adding Emil, Rob, and Rob]
>>> >>>
>>> >>> Hi,
>>> >>> Ok, I've signed up for the android-x86 list. I don't anticipate
>>> >>> seeing all
>>> >>> posts, so please cc me on threads needing feedback.
>>> >>>
>>> >>> We also just today open-sourced drm_hwcomposer on the chromium gerrit
>>> >>> instance, such that we'll be doing all of our development in the open
>>> >>> on
>>> >>> that repo.
>>> >>>
>>> >>> The repo is here:
>>> >>> https://chromium.googlesource.com/chromiumos/drm_hwcomposer
>>> >>>
>>> >>> Contributing instructions are here:
>>> >>>
>>> >>> https://sites.google.com/a/chromium.org/dev/contributing-to-drm_hwcomposer
>>> >>
>>> >> Thanks for the pointer. This is essentially what I'm based on.
>>> >>
>>> >> Is there a testing target we need to use for submitting patches? Pixel
>>> >> C? The first problem is the use of the pre mainline atomic functions,
>>>
>>> Dear Sean,
>>> I echo Rob's words.
>>> We planned to use kernel 4.4 and libdrm 2.4.66+
>>> for marshmallow-x86.
>>> Do you have an updated drm_gralloc that
>>> can work with libdrm 2.4.66+?
>>
>>
>> No.
>>
>>
>>>
>>> Or do you hope me to submit a patch for it?
>>>
>>> >> so using mainline kernel and libdrm are a problem. What is your plan
>>> >> to handle that?
>>
>>
>> I'll look at updating android's libdrm today. In the long term, we're
>> hoping to centralize libdrm between cros and android much like
>> drm_hwcomposer, but there are still some moving parts that have yet to be
>> sorted out.
>>
>> Once libdrm is updated, we can look at getting robh's patch in.
>>
>
> I just updated Android's libdrm to 2.4.66, there's a mirror here:
> https://github.com/crseanpaul/libdrm/tree/merge-2.4.66
>
> The old and new atomic apis are beside each other. Once we have
> drm_hwcomposer using the new atomic apis, I'll remove the old ones from
> libdrm.
>
> robh, can you please upload your drm_hwcomposer to gerrit so we can get it
> merged?

I assume you get notified, but in case not I've submitted 2 patches.

Rob