On 1/9/25 10:25 AM, Hecht, Martin (Avnet Silica) via lists.yoctoproject.org 
wrote:
Hi Mark and Tony,

just a question regarding current status of mali support of the BSP 2024.2.

You need to be sure your project includes the meta-xilinx-mali400 layer. This includes all of the support for the mali400 that is in the ZynqMP EG and EV line.

See the README.md file in that layer for more information.

I'm used to have the proprietary mali userspace lib since we enable Weston and libgbm many years ago together with your colleagues (Alok Gupta and Kwon Hyun) .

Both the proprietary and open source (mesa-lima) support is available. When using PetaLinux, the proprietary mali driver is defaulted. If you are using a different distribution you will need to enable it as the open source library is the default.

In short, open source driver (and proprietary) is enabled when the machine includes the MACHINE_FEATURES of 'mali400'. Then the proprietary driver is further enabled with a DISTRO_FEATURES that includes "libmali".

There are both advantages and disadvantages of both the proprietary and open source drivers, thus we enable the use of both of them, but they are mutually exclusive in your filesystem -- so you will need to decide which to use.

So far I remember I could get it running with 2023.1 too (with weston 9).

Weston newer then 9 requires OpenGL/mesa interfaces that are not provided by the proprietary libmali driver. The layer provides a port of Weston 9 for use with the proprietary driver, but also allows Weston 13 (in scarthgap/2024.2) to be used if you are using the open source mesa-lima.

I never tested lima before. But since 2024.1 and 2024.1 I can't get weston running when buidling core-image-weston even also with distro petalinux.

Your machine and distro both need to be enabled with the FEATURES I mentioned above. In 2024.2, we explicitly moved this out to make it clear what is being done for mali support, as many users will not need it.

Also I can't get glmark2-es2-drm running on kms as I used to run. Same for 
kmscube.

I'd suggest reporting this through the normal AMD support methods. I have limited experience executing the glmark2 demos, so I'm not sure what is and isn't supported and the ramifications of this.

I'm working on a customer demo were I need to use the gpu for online and offline rendering for video streams in realtime. I did this in past with a similar approach as kmscube over several releases since probably 2018.x. So it was possible to use the Mali GPU for video transformation (2D, 3D) and mixing multiple layers  in gstreamer ....

In weston I was also able with the older BSP's to adjust the bpp of the video memory in dts as well in weston to use 32bpp.

Currently I'm struggeling  because I can't use drm correctly.

Can someone confirm that weston and glmark2 works in 2024.2? I tried both mali configurations on zcu106 as described in sources/meta-xilinx/meta-xilinx-mali400/README.md .


I'm not familiar with all of the ways that the mali400 is being used. I would expect if it worked in the past it should still work, at least in the context of the proprietary driver.

If you are using the ZynqMP EV, then you also need to ensure that you have enabled the 'vcu' support and are using it with gstreamer for the highest performance. But beyond that I don't have much experience with it to add more details. I think the AMD forums may be better equipped to answer specific questions about using the components for the best experience.

--Mark


Thank you very much in advance.

BR Martin

We continuously commit to comply with the applicable data protection laws and ensure fair and transparent processing of your personal data. Please read our privacy statement including an information notice and data protection policy for detailed information on our website.





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5523): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5523
Mute This Topic: https://lists.yoctoproject.org/mt/110518823/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

  • [meta-xilinx] wron... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
    • [meta-xilinx]... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
    • Re: [meta-xil... Mark Hatle
      • Re: [meta... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
      • [meta-xil... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
        • Re: [... Mark Hatle
          • R... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
            • ... Mark Hatle
            • ... Mark Hatle
              • ... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
              • ... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
                • ... Mark Hatle
                • ... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
                • ... Mark Hatle
                • ... Hecht, Martin (Avnet Silica) via lists.yoctoproject.org
                • ... Kohn, Chris via lists.yoctoproject.org

Reply via email to