Hi,
Just for you to know. I opened an issue on Mesa's gitalb too about the
regression https://gitlab.freedesktop.org/mesa/mesa/-/issues/11105.
Thanks for the help.
Regards,
João Paulo Gonçalves
On Thu, Apr 25, 2024 at 9:08 AM Lucas Stach wrote:
> I can reproduce the issue, but sadly there is no simple fix for this,
> as it's a bad interaction between some of the new features.
> At the core of the issue is the dmabuf-feedback support with the chain
> of events being as follows:
> 1.
On Thu, Apr 25, 2024 at 5:58 AM Lucas Stach wrote:
> Etnaviv added some resource tracking to fix issues with a number of
> use-cases, which did add some CPU overhead and might cost some
> performance, but should no be as dramatic as the numbers you are seeing
> here.
Good to know. Thanks!
>
Hello all,
We might have encountered a performance regression after upgrading from Mesa
2022.0.3 to 2024.0.2. During our automated hardware tests using LAVA, we noticed
a lower score on glmark2 when we upgraded from the OpenEmbedded release from
Kirkstone to Scartgarth. After conducting some
Ok.
I am starting to think that this can be a version problem. My .xsa is from
vivado 2020.1 and i am trying to use 2022.2 releases from meta-xilinx.
Sandeep, indeed my uart 1 is not enabled on Vivado design. I will try to use
uart 0. As soon i do that, i will update the result here.
Thanks
Hi , Grzegorz.
I changed HAS_PLATFORM_INIT to *HAS_PLATFORM_INIT = xilinx_zynqmp_virt_config*
(as my board is based on zynqmp ) but the error remains and still the same.
I think that this is not the problem. The files in HAS_PLATFORM_INIT are u-boot
defconfigs and seem to be used to add init
