[Mesa-dev] [android-x86-devel] Re: gralloc_drm_pipe
cwhuang at android-x86.org
Wed Apr 6 16:12:57 UTC 2016
2016-04-04 6:25 GMT+08:00 Rob Herring <robherring2 at gmail.com>:
> On Sun, Apr 3, 2016 at 12:29 PM, Chih-Wei Huang <cwhuang at android-x86.org> wrote:
>> Besides, the module name is still gralloc.drm.
>> How about call it gralloc.gbm?
> Eventually yes, but for now it is more convenient for my development
> to keep the name the same.
>> That means it can coexist with the current
>> gralloc.drm module so the transition to it
>> will be easier. Agree?
> It's not binary compatible, only source compatible ATM, so they can't
> really coexist yet. The gralloc implementation specific dependencies
The co-existence means to put the two gralloc
implementations in the same image and
select which one to be used by GPU at runtime.
This is carried out by our init.sh like
case "$(cat /proc/fb | head -1)" in
set_property ro.hardware.gralloc gbm
set_property ro.hardware.hwcomposer drm
set_property ro.hardware.gralloc drm
They don't need to be binary or source compatible, I think.
I guess the first supported GPU is virgl. Right?
When could we expect it's ready to test?
> in mesa and hwc is something I'm looking at. They consist of
> retrieving the prime FD for a handle and retrieving the DRM device FD.
More information about the mesa-dev