[Mesa-dev] GALLIUM_HUD issue with Android
cphealy at gmail.com
Mon Aug 7 18:53:21 UTC 2017
I believe you are correct Rob. I grabbed a dumpsys from
SurfaceFlinger and put the output here:
This was done with a game running in the foreground with the 38 pixel
high navigation bar still present on the bottom of the screen.
It seems to me that we need some way with the HUD to have it only
applied to the final composition of all the surfaces that
SurfaceFlinger flings to drm_hwcomposer. (At least that's what I
think from my naive understanding of things.)
On Fri, Aug 4, 2017 at 5:38 AM, Rob Clark <robdclark at gmail.com> wrote:
> afaict this is more or less the case w/ android.. top/bottom bar,
> search bar, wallpaper, etc, are all pushed to surface-flinger as
> separate "windows"..
> Try "adb shell dumpsys SurfaceFlinger" with an android device. (I'm
> not 100% sure if you need root to do that.)
> And with android forking everything (or at least nearly everything)
> from zygote process, I'm not entirely sure how target environment
> variables to specific processes. :-/
> On Thu, Aug 3, 2017 at 6:24 PM, Marek Olšák <maraeo at gmail.com> wrote:
>> Hi Chris,
>> The HUD is drawn inside SwapBuffers. It shouldn't be in every widget
>> unless every widget is a separate double-buffered GL window.
>> On Thu, Aug 3, 2017 at 6:50 PM, Chris Healy <cphealy at gmail.com> wrote:
>>> Running Android on top of Mesa has exposed an issue with the
>>> GALLIUM_HUD where we get the HUD graphs rendered to each of the
>>> surfaces that Android is working with, so there is one with the top
>>> bar, one with the bottom bar, one with the main surface, and even one
>>> with popups.
>>> I'm looking to get some insight into how best to address this issue
>>> with the HUD code when working on Android systems as the HUD is still
>>> quite useful when running Android.
>>> mesa-dev mailing list
>>> mesa-dev at lists.freedesktop.org
>> mesa-dev mailing list
>> mesa-dev at lists.freedesktop.org
More information about the mesa-dev