From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: Build core-image-weston for beaglebone/am335x with GPU SGX530 enabled To: meta-ti@lists.yoctoproject.org From: "Luca" X-Originating-Location: Arzignano, Veneto, IT (185.23.87.190) X-Originating-Platform: Windows Chrome 81 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Mon, 18 May 2020 12:19:19 -0700 References: In-Reply-To: Message-ID: <16879.1589829559511127279@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="rSI1q5ui2Vcq7GtgcvSw" --rSI1q5ui2Vcq7GtgcvSw Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Andrew, thanks a lot for the clarifications and updated info. It seems I was relaying on outaded and/or incomplete info. >=20 > libgbm is a virtual as it has multiple optional providers, one of which > is ti-sgx-ddk-um, our standalone libgbm has been deprecated, use the one > provided by ti-sgx-ddk-um: >=20 > PREFERRED_PROVIDER_virtual/libgbm =3D "ti-sgx-ddk-um" >=20 Perfect, thanks. I was just starting to understand that the standalone lib= gbm has been deprecated reading http://software-dl.ti.com/processor-sdk-lin= ux/esd/docs/latest/linux/Foundational_Components/Graphics/Migration_From_Pr= ior_Releases.html#from-processor-sdk-6-1-to-6-2-for-am3-4-5-6 >=20 > EGL provides window system (x11, wayland, gbm, surfaceless) integration > for both GL and GLES (and OpenVG), but our EGL implementation only > supports GLES, as that is all our GPUs support (at least on AM335x). > Full desktop GL would have to be done using SW rendering, which is > probably not what you want. I understood that full GL would have been done using SW rendering, but I t= hought it was the only way to get Weston working. >=20 > So my question back is then, why are you trying to pull in 'mesa' and/or > 'mesa-gl'? Weston works fine with the stack we provide in ti-sgx-ddk-um. >=20 Your question is very legitimate. I was pulling mesa-gl just to fulfil Weston dependencies, but thank to you= r info I now understand that I was doing it the wrong way. Then the question is: How should I set the providers to get Weston working fine with ti-sgx-ddk-= um? Regards Luca --rSI1q5ui2Vcq7GtgcvSw Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Andrew,

thanks a lot for the clarifications and updated info.=
It seems I was relaying on outaded and/or incomplete info.

libgbm is a virtual as = it has multiple optional providers, one of which
is ti-sgx-ddk-um, our standalone libgbm has been d= eprecated, use the one
<= /span>provided by ti-sgx-ddk-um:
PREFERRED_PROVIDER_virtual/libgbm = =3D "ti-sgx-ddk-um"
Perfect, thanks. I was just starting to understand that the standalone lib= gbm has been deprecated reading http://software-dl.ti.com/processor-= sdk-linux/esd/docs/latest/linux/Foundational_Components/Graphics/Migration_= From_Prior_Releases.html#from-processor-sdk-6-1-to-6-2-for-am3-4-5-6
EGL provides window sys= tem (x11, wayland, gbm, surfaceless) integration
for both GL and GLES (and OpenVG), but our EGL imp= lementation only
support= s GLES, as that is all our GPUs support (at least on AM335x).
<= span style=3D"white-space: pre-wrap;">Full desktop GL would have to be done= using SW rendering, which is
probably not what you want.
I understood that full GL would have been done using SW rendering, but I t= hought it was the only way to get Weston working.

So my question back is = then, why are you trying to pull in 'mesa' and/or
'mesa-gl'? Westo= n works fine with the stack we provide in ti-sgx-ddk-um.
 Your question is very legitimate.
I was pulling mesa-gl just to fulfi= l Weston dependencies, but thank to your info I now understand that I was d= oing it the wrong way.
Then the question is:
How should I set the= providers to get Weston working fine with ti-sgx-ddk-um?

Regards
Luca

<= br />
 --rSI1q5ui2Vcq7GtgcvSw--