[Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi, We are working on iMx53 Quick start board based on iMx53 application processor. As you know this has A200 GPU. If I see in the mainline kernel 4.11.3, there are no source files for A2XX GPU. Based on this I am assuming that the mainline doesn't have support for A2XX. However in kernel-msm git checkout from Freedreno, there are A2XX related source code. I wanted to know whether this code is tested one and reason for non-inclusion of this code in mainline kernel. Are there any pointers how I can go about it. Thank you very much :) Regards, Abhijit ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
On Wed, May 31, 2017 at 9:42 AM, abhijit wrote: > However in kernel-msm git checkout from Freedreno, there are A2XX related > source code. I wanted to know whether this code is tested one and reason for > non-inclusion of this code in mainline kernel. which branch/tree are you referring to here? ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
On Wed, May 31, 2017 at 3:42 AM, abhijit wrote: > Hi, > > We are working on iMx53 Quick start board based on iMx53 application > processor. As you know this has A200 GPU. > > If I see in the mainline kernel 4.11.3, there are no source files for A2XX > GPU. Based on this I am assuming that the mainline doesn't have support for > A2XX. > > However in kernel-msm git checkout from Freedreno, there are A2XX related > source code. I wanted to know whether this code is tested one and reason for > non-inclusion of this code in mainline kernel. With the kgsl backend in libdrm_freedreno, the userspace mesa driver can work with some specific of kgsl (drivers/gpu/msm) from downstream kernel-msm tree.. that kind of involves some hacks that don't work perfectly to fake implicit-sync. And I think downstream api changed over time, I don't think many have had much luck getting that working on newer android kernel branches. As far as upstream driver (drivers/gpu/drm/msm), no one has sent patches, yet. Someone would need to study the a2xx parts in downstream kernel and figure out how to add that in drm/msm/adreno. Since the gpummu is part of the gpu (rather than a separate iommu block with iommu driver outside of drm/msm), that would also need to be ported. If you have a setup w/ the downstream kernel driver working (for example on an old kernel), doing something approximately like this[1] could be useful to log clock/regulator/register access. The demsm tool in freedreno envytools tree[2] can decode the logged registers to make it easier to read. Note, there have been some mesa patches on userspace side to make things work better on a20x variants (previously I only had a22x devices), although I don't think I've seen those posted to mesa-devel yet. [1] https://github.com/freedreno/kernel-msm/commit/814a28f5cedc8621fe746b601dd51d5869931845 [2] https://github.com/freedreno/envytools/blob/master/rnn/demsm.c BR, -R > Are there any pointers how I can go about it. > > Thank you very much :) > > Regards, > Abhijit > ___ > Freedreno mailing list > Freedreno@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/freedreno ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Rob and Nicolas, Thank you very much for your replies. On Wednesday 31 May 2017 05:45 PM, Rob Clark wrote: On Wed, May 31, 2017 at 3:42 AM, abhijit wrote: Hi, We are working on iMx53 Quick start board based on iMx53 application processor. As you know this has A200 GPU. If I see in the mainline kernel 4.11.3, there are no source files for A2XX GPU. Based on this I am assuming that the mainline doesn't have support for A2XX. However in kernel-msm git checkout from Freedreno, there are A2XX related source code. I wanted to know whether this code is tested one and reason for non-inclusion of this code in mainline kernel. With the kgsl backend in libdrm_freedreno, the userspace mesa driver can work with some specific of kgsl (drivers/gpu/msm) from downstream kernel-msm tree.. that kind of involves some hacks that don't work perfectly to fake implicit-sync. And I think downstream api changed over time, I don't think many have had much luck getting that working on newer android kernel branches. Actually I am new to GPU technology. Can you please point to some links w.r.t implicit-sync.. As far as upstream driver (drivers/gpu/drm/msm), no one has sent patches, yet. Someone would need to study the a2xx parts in downstream kernel and figure out how to add that in drm/msm/adreno. Since the gpummu is part of the gpu (rather than a separate iommu block with iommu driver outside of drm/msm), that would also need to be ported. Does IOMMU supported in downstream kernel? Actually instead of porting the driver to upstream kernel, I was thinking about building these components as loadable modules and using it in the upstream kernel, as we have very less time w.r.t this activity. If we are successful, we can take it as starting point for putting things together for porting. Following is the approach I want to take for getting A200 to work on upstream kernel, based on suggestion by Rob, 1. Get working old binary only GPU driver to work on the board and get clock and register values. 2. These clock values can be passed from Device tree entries or platform data when booting it from main-line kernel 3. Build Gallium dri component, drm component and driver component(KGSL) for upstream kernel(Only OPENGL path with KGSL approach) I am comparing upstream stream Linux kernel provided by Freescale for i.mx53 QSB. The kernel version is 4.11.3. The downstream kernel is, freedreno git repository "https://github.com/freedreno/kernel-msm.git";, this repository and I am on hp-tenderloin-3.0 branch, which is android kernel. Please let me know if my understanding is correct. If you have a setup w/ the downstream kernel driver working (for example on an old kernel), doing something approximately like this[1] could be useful to log clock/regulator/register access. The demsm tool in freedreno envytools tree[2] can decode the logged registers to make it easier to read. Note, there have been some mesa patches on userspace side to make things work better on a20x variants (previously I only had a22x devices), although I don't think I've seen those posted to mesa-devel yet. [1] https://github.com/freedreno/kernel-msm/commit/814a28f5cedc8621fe746b601dd51d5869931845 [2] https://github.com/freedreno/envytools/blob/master/rnn/demsm.c BR, -R Are there any pointers how I can go about it. Thank you very much :) Regards, Abhijit ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno Regards, Abhijit ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi, I needed some help with respect to binding of freedreno driver to mesa I have cross compiled freedreno driver for A2XX with main line kernel and added clocking info referring driver from TQ-Embedded "https://www.tq-group.com/en/support/download /?tx_abdownloads_pi1%5Baction%5D=getviewcategory&tx_abdownloads_pi1%5Bcategory_uid%5D=672&tx_abdownloads_pi1%5Bcid%5D=84&tx_abdownloads_pi1%5Bpointer%5D=1&cHash=5e7c087ae16a9426fc0353db0042615a" I also cross-compiled, libdrm and mesa components from freedreno git hub But when I am running "glxinfo" command to verify whether underlaying 3D acceleration is being used, I am observing that softpipe is being used instead of "freedreno" I figured it out that glxinfo uses mesa/src/mesa/drivers/dri/swrast as user side driver component Files under /src/mesa/drivers/dri use "_mesa_initialize_context" to register them self to mesa component. But I am not seeing any freedreno related source files calling "_mesa_initialize_context" Can you please let me know whether I have to add mesa related functionalities for freedreno or there some other alternatives? Thank you very much :) On Wednesday 31 May 2017 01:12 PM, abhijit wrote: Hi, We are working on iMx53 Quick start board based on iMx53 application processor. As you know this has A200 GPU. If I see in the mainline kernel 4.11.3, there are no source files for A2XX GPU. Based on this I am assuming that the mainline doesn't have support for A2XX. However in kernel-msm git checkout from Freedreno, there are A2XX related source code. I wanted to know whether this code is tested one and reason for non-inclusion of this code in mainline kernel. Are there any pointers how I can go about it. Thank you very much :) Regards, Abhijit ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
The most obvious thing to check is make sure you use --enable-freedreno-kgsl when building libdrm.. if you have that, then try: LIBGL_DEBUG=verbose glxinfo BR, -R On Sat, Jul 8, 2017 at 2:07 AM, abhijit wrote: > Hi, > > I needed some help with respect to binding of freedreno driver to mesa > > I have cross compiled freedreno driver for A2XX with main line kernel and > added clocking info referring driver from TQ-Embedded > "https://www.tq-group.com/en/support/download > /?tx_abdownloads_pi1%5Baction%5D=getviewcategory&tx_abdownloads_pi1%5Bcategory_uid%5D=672&tx_abdownloads_pi1%5Bcid%5D=84&tx_abdownloads_pi1%5Bpointer%5D=1&cHash=5e7c087ae16a9426fc0353db0042615a" > > I also cross-compiled, libdrm and mesa components from freedreno git hub > > But when I am running "glxinfo" command to verify whether underlaying 3D > acceleration is being used, I am observing that softpipe is being used > instead of "freedreno" > > I figured it out that glxinfo uses mesa/src/mesa/drivers/dri/swrast as user > side driver component > > Files under /src/mesa/drivers/dri use "_mesa_initialize_context" to register > them self to mesa component. But I am not seeing any freedreno related > source files calling "_mesa_initialize_context" > > Can you please let me know whether I have to add mesa related > functionalities for freedreno or there some other alternatives? > > Thank you very much :) > > On Wednesday 31 May 2017 01:12 PM, abhijit wrote: >> >> Hi, >> >> We are working on iMx53 Quick start board based on iMx53 application >> processor. As you know this has A200 GPU. >> >> If I see in the mainline kernel 4.11.3, there are no source files for >> A2XX GPU. Based on this I am assuming that the mainline doesn't have >> support for A2XX. >> >> However in kernel-msm git checkout from Freedreno, there are A2XX >> related source code. I wanted to know whether this code is tested one >> and reason for non-inclusion of this code in mainline kernel. >> >> Are there any pointers how I can go about it. >> >> Thank you very much :) >> >> Regards, >> Abhijit > > ___ > Freedreno mailing list > Freedreno@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/freedreno ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 But still gallium component of freedreno is not building. For example, r600_dri.so and r300_dri.so are build but freedreno_dri.so is not build. I verified that the source code of freedreno is compiling though Setting LIBGL_DEBUG=verbose, is not showing any additional logs. However, software pipe is being used for rendering On Sunday 09 July 2017 10:48 PM, Rob Clark wrote: The most obvious thing to check is make sure you use --enable-freedreno-kgsl when building libdrm.. if you have that, then try: LIBGL_DEBUG=verbose glxinfo BR, -R On Sat, Jul 8, 2017 at 2:07 AM, abhijit wrote: Hi, I needed some help with respect to binding of freedreno driver to mesa I have cross compiled freedreno driver for A2XX with main line kernel and added clocking info referring driver from TQ-Embedded "https://www.tq-group.com/en/support/download /?tx_abdownloads_pi1%5Baction%5D=getviewcategory&tx_abdownloads_pi1%5Bcategory_uid%5D=672&tx_abdownloads_pi1%5Bcid%5D=84&tx_abdownloads_pi1%5Bpointer%5D=1&cHash=5e7c087ae16a9426fc0353db0042615a" I also cross-compiled, libdrm and mesa components from freedreno git hub But when I am running "glxinfo" command to verify whether underlaying 3D acceleration is being used, I am observing that softpipe is being used instead of "freedreno" I figured it out that glxinfo uses mesa/src/mesa/drivers/dri/swrast as user side driver component Files under /src/mesa/drivers/dri use "_mesa_initialize_context" to register them self to mesa component. But I am not seeing any freedreno related source files calling "_mesa_initialize_context" Can you please let me know whether I have to add mesa related functionalities for freedreno or there some other alternatives? Thank you very much :) On Wednesday 31 May 2017 01:12 PM, abhijit wrote: Hi, We are working on iMx53 Quick start board based on iMx53 application processor. As you know this has A200 GPU. If I see in the mainline kernel 4.11.3, there are no source files for A2XX GPU. Based on this I am assuming that the mainline doesn't have support for A2XX. However in kernel-msm git checkout from Freedreno, there are A2XX related source code. I wanted to know whether this code is tested one and reason for non-inclusion of this code in mainline kernel. Are there any pointers how I can go about it. Thank you very much :) Regards, Abhijit ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: > Hi Rob, > > Thank you very much for your reply. > > I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the > same is copied to target > > The issue seems to be in mesa build > > I observed that there are two mechanism in which application can interact > with underlaying DRM, > 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) > 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) > > Freedreno driver is present only in Case 2. For that reason I disabled dri > in Mesa build and enabled gallium-xlib intreface, which will enable case 2 You absolutely need --enable-dri. Gallium drivers are also DRI drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, while the others are "gallium" drivers. However they're all DRI drivers. You can build mesa --with-dri-drivers="" --with-gallium-drivers="freedreno", but you have to leave DRI(3) enabled. -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Ilia, Thank you very much for your reply. I am able to create msm_dri.so file with options you provided Even after that, soft pipe is being used for rendering. I am suspecting that glxinfo will use driver depending on _drv.so being detected by xinit Now I have freedreno_drv.so too. But still soft pipe is being used. I am trying to solve this puzzle. Warm Regards, Abhijit On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 You absolutely need --enable-dri. Gallium drivers are also DRI drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, while the others are "gallium" drivers. However they're all DRI drivers. You can build mesa --with-dri-drivers="" --with-gallium-drivers="freedreno", but you have to leave DRI(3) enabled. -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi all, Running xinit load freedreno_drv.so file after adding configuration in /etc/X11/xorg.conf, Section "Server Flags" Option "IgnoreABI" EndSection Section "Device" Identifier "Device0" Driver "freedreno" VendorName "Freedreno " BoardName "SoC" EndSection But I am getting segmentaion fault and following is snippet of /var/log/Xorg.0.log [ 6587.058] (II) No msm DRM/KMS, fallback to fbdev/kgsl [ 6587.059] [ 6587.059] Backtrace: [ 6587.059] [ 6587.059] Segmentation fault at address 0x3 [ 6587.059] Fatal server error: [ 6587.059] Caught signal 11 (Segmentation fault). Server aborting Please let me know how I can go about debugging it On Friday 14 July 2017 01:13 PM, abhijit naik wrote: Hi Ilia, Thank you very much for your reply. I am able to create msm_dri.so file with options you provided Even after that, soft pipe is being used for rendering. I am suspecting that glxinfo will use driver depending on _drv.so being detected by xinit Now I have freedreno_drv.so too. But still soft pipe is being used. I am trying to solve this puzzle. Warm Regards, Abhijit On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 You absolutely need --enable-dri. Gallium drivers are also DRI drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, while the others are "gallium" drivers. However they're all DRI drivers. You can build mesa --with-dri-drivers="" --with-gallium-drivers="freedreno", but you have to leave DRI(3) enabled. -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
On Fri, Jul 14, 2017 at 6:52 AM, abhijit wrote: > Hi all, > > Running xinit load freedreno_drv.so file after adding configuration in > /etc/X11/xorg.conf, > > Section "Server Flags" > Option "IgnoreABI" > EndSection > > Section "Device" > Identifier "Device0" > Driver "freedreno" > VendorName "Freedreno " > BoardName "SoC" > EndSection > > But I am getting segmentaion fault and following is snippet of > /var/log/Xorg.0.log > > [ 6587.058] (II) No msm DRM/KMS, fallback to fbdev/kgsl > [ 6587.059] > [ 6587.059] Backtrace: > [ 6587.059] > [ 6587.059] Segmentation fault at address 0x3 > [ 6587.059] > Fatal server error: > [ 6587.059] Caught signal 11 (Segmentation fault). Server aborting > > Please let me know how I can go about debugging it > well, IgnoreABI is more than a bit scary.. the old downstream msm fdbdev driver wasn't a bit non-standard, so there might be issues w/ xf86-video-freedreno working w/ a different fbdev driver (not to mention the non-KMS codepaths probably haven't been exercised in a while). But I suspect an ABI mismatch between xf86-video-freedreno is likely to cause more problems. BR, -R > > On Friday 14 July 2017 01:13 PM, abhijit naik wrote: >> >> Hi Ilia, >> >> Thank you very much for your reply. >> >> I am able to create msm_dri.so file with options you provided >> >> Even after that, soft pipe is being used for rendering. >> >> I am suspecting that glxinfo will use driver depending on _drv.so being >> detected by xinit >> >> Now I have freedreno_drv.so too. But still soft pipe is being used. I am >> trying to solve this puzzle. >> >> Warm Regards, >> Abhijit >> >>> On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: >>> On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 >>> >>> >>> You absolutely need --enable-dri. Gallium drivers are also DRI >>> drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, >>> while the others are "gallium" drivers. However they're all DRI >>> drivers. >>> >>> You can build mesa --with-dri-drivers="" >>> --with-gallium-drivers="freedreno", but you have to leave DRI(3) >>> enabled. >>> >>> -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi All :) Finally I am able to get freedreno_drv.so and xserver ABI version to get matched. I am using buildroot to get the proper package dependency and build. Currently our target has following binaries, $(ROOT_DIR)/usr/lib/xorg/modules/drivers/freedreno_drv.so $(ROOT_DIR)/usr/lib/dri/msm_dri.so $(ROOT_DIR)/usr/lib/libdrm_freedreno.so I also loaded msm_kgsl_core.ko and msm_adreno.ko But my xinit is giving following output "[ 233.794] (WW) Falling back to old probe method for freedreno" "[ 233.831] (II) No msm DRM/KMS, fallback to fbdev/kgsl" "[ 234.801] (II) UnloadModule: "freedreno"" "[ 234.801] (II) Unloading freedreno" Referring to freedreno architecture, I interpreted kgsl must be enabled in the libdrm and enabled same. But still freedreno module is getting unloaded I will be grateful if any body can give lead on this. Regards, Abhijit On Friday 14 July 2017 05:28 PM, Rob Clark wrote: On Fri, Jul 14, 2017 at 6:52 AM, abhijit wrote: Hi all, Running xinit load freedreno_drv.so file after adding configuration in /etc/X11/xorg.conf, Section "Server Flags" Option "IgnoreABI" EndSection Section "Device" Identifier "Device0" Driver "freedreno" VendorName "Freedreno " BoardName "SoC" EndSection But I am getting segmentaion fault and following is snippet of /var/log/Xorg.0.log [ 6587.058] (II) No msm DRM/KMS, fallback to fbdev/kgsl [ 6587.059] [ 6587.059] Backtrace: [ 6587.059] [ 6587.059] Segmentation fault at address 0x3 [ 6587.059] Fatal server error: [ 6587.059] Caught signal 11 (Segmentation fault). Server aborting Please let me know how I can go about debugging it well, IgnoreABI is more than a bit scary.. the old downstream msm fdbdev driver wasn't a bit non-standard, so there might be issues w/ xf86-video-freedreno working w/ a different fbdev driver (not to mention the non-KMS codepaths probably haven't been exercised in a while). But I suspect an ABI mismatch between xf86-video-freedreno is likely to cause more problems. BR, -R On Friday 14 July 2017 01:13 PM, abhijit naik wrote: Hi Ilia, Thank you very much for your reply. I am able to create msm_dri.so file with options you provided Even after that, soft pipe is being used for rendering. I am suspecting that glxinfo will use driver depending on _drv.so being detected by xinit Now I have freedreno_drv.so too. But still soft pipe is being used. I am trying to solve this puzzle. Warm Regards, Abhijit On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 You absolutely need --enable-dri. Gallium drivers are also DRI drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, while the others are "gallium" drivers. However they're all DRI drivers. You can build mesa --with-dri-drivers="" --with-gallium-drivers="freedreno", but you have to leave DRI(3) enabled. -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
On Thu, Aug 3, 2017 at 8:23 AM, abhijit wrote: > Hi All :) > > Finally I am able to get freedreno_drv.so and xserver ABI version to get > matched. > > I am using buildroot to get the proper package dependency and build. > > Currently our target has following binaries, > $(ROOT_DIR)/usr/lib/xorg/modules/drivers/freedreno_drv.so > $(ROOT_DIR)/usr/lib/dri/msm_dri.so > $(ROOT_DIR)/usr/lib/libdrm_freedreno.so > > I also loaded msm_kgsl_core.ko and msm_adreno.ko > > But my xinit is giving following output > "[ 233.794] (WW) Falling back to old probe method for freedreno" > "[ 233.831] (II) No msm DRM/KMS, fallback to fbdev/kgsl" > I guess that it is failing to find the old kgsl shim drm driver, which enabled allocation of GEM buffers for pixmaps. I know Wladimir played a bit with this on imx5, but I think he was just using gbm/kms and not x11. I guess he was using imx-drm for GEM buffer allocation? BR, -R > "[ 234.801] (II) UnloadModule: "freedreno"" > "[ 234.801] (II) Unloading freedreno" > > Referring to freedreno architecture, I interpreted kgsl must be enabled in > the libdrm and enabled same. But still freedreno module is getting unloaded > > I will be grateful if any body can give lead on this. > > Regards, >Abhijit > > > On Friday 14 July 2017 05:28 PM, Rob Clark wrote: >> >> On Fri, Jul 14, 2017 at 6:52 AM, abhijit wrote: >>> >>> Hi all, >>> >>> Running xinit load freedreno_drv.so file after adding configuration in >>> /etc/X11/xorg.conf, >>> >>> Section "Server Flags" >>> Option "IgnoreABI" >>> EndSection >>> >>> Section "Device" >>> Identifier "Device0" >>> Driver "freedreno" >>> VendorName "Freedreno " >>> BoardName "SoC" >>> EndSection >>> >>> But I am getting segmentaion fault and following is snippet of >>> /var/log/Xorg.0.log >>> >>> [ 6587.058] (II) No msm DRM/KMS, fallback to fbdev/kgsl >>> [ 6587.059] >>> [ 6587.059] Backtrace: >>> [ 6587.059] >>> [ 6587.059] Segmentation fault at address 0x3 >>> [ 6587.059] >>> Fatal server error: >>> [ 6587.059] Caught signal 11 (Segmentation fault). Server aborting >>> >>> Please let me know how I can go about debugging it >>> >> >> well, IgnoreABI is more than a bit scary.. the old downstream msm >> fdbdev driver wasn't a bit non-standard, so there might be issues w/ >> xf86-video-freedreno working w/ a different fbdev driver (not to >> mention the non-KMS codepaths probably haven't been exercised in a >> while). But I suspect an ABI mismatch between xf86-video-freedreno is >> likely to cause more problems. >> >> BR, >> -R >> >> >>> >>> On Friday 14 July 2017 01:13 PM, abhijit naik wrote: Hi Ilia, Thank you very much for your reply. I am able to create msm_dri.so file with options you provided Even after that, soft pipe is being used for rendering. I am suspecting that glxinfo will use driver depending on _drv.so being detected by xinit Now I have freedreno_drv.so too. But still soft pipe is being used. I am trying to solve this puzzle. Warm Regards, Abhijit > On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: > >> On Mon, Jul 10, 2017 at 10:53 AM, abhijit >> wrote: >> Hi Rob, >> >> Thank you very much for your reply. >> >> I ensured that --enable-freedreno-kgsl is enabled in libdrm build and >> the >> same is copied to target >> >> The issue seems to be in mesa build >> >> I observed that there are two mechanism in which application can >> interact >> with underlaying DRM, >>1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) >>2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) >> >> Freedreno driver is present only in Case 2. For that reason I >> disabled dri >> in Mesa build and enabled gallium-xlib intreface, which will enable >> case 2 > > > > You absolutely need --enable-dri. Gallium drivers are also DRI > drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, > while the others are "gallium" drivers. However they're all DRI > drivers. > > You can build mesa --with-dri-drivers="" > --with-gallium-drivers="freedreno", but you have to leave DRI(3) > enabled. > > -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Rob, Thank you very much for information. Actually I am not constrained to use X server. But can you please let me know what are the components that may be needed for testing freedreno test applications, apart from libdrm and mesa? I thought X may be needed for graphic drawing. Sorry if the questions are too basic. Actually I am getting overwhelmed with lot of options available and I am not getting what is the right way to proceed... I will try get something to work with GBM though Regards, Abhijit On Sunday 06 August 2017 04:32 PM, Rob Clark wrote: On Thu, Aug 3, 2017 at 8:23 AM, abhijit wrote: Hi All :) Finally I am able to get freedreno_drv.so and xserver ABI version to get matched. I am using buildroot to get the proper package dependency and build. Currently our target has following binaries, $(ROOT_DIR)/usr/lib/xorg/modules/drivers/freedreno_drv.so $(ROOT_DIR)/usr/lib/dri/msm_dri.so $(ROOT_DIR)/usr/lib/libdrm_freedreno.so I also loaded msm_kgsl_core.ko and msm_adreno.ko But my xinit is giving following output "[ 233.794] (WW) Falling back to old probe method for freedreno" "[ 233.831] (II) No msm DRM/KMS, fallback to fbdev/kgsl" I guess that it is failing to find the old kgsl shim drm driver, which enabled allocation of GEM buffers for pixmaps. I know Wladimir played a bit with this on imx5, but I think he was just using gbm/kms and not x11. I guess he was using imx-drm for GEM buffer allocation? BR, -R "[ 234.801] (II) UnloadModule: "freedreno"" "[ 234.801] (II) Unloading freedreno" Referring to freedreno architecture, I interpreted kgsl must be enabled in the libdrm and enabled same. But still freedreno module is getting unloaded I will be grateful if any body can give lead on this. Regards, Abhijit On Friday 14 July 2017 05:28 PM, Rob Clark wrote: On Fri, Jul 14, 2017 at 6:52 AM, abhijit wrote: Hi all, Running xinit load freedreno_drv.so file after adding configuration in /etc/X11/xorg.conf, Section "Server Flags" Option "IgnoreABI" EndSection Section "Device" Identifier "Device0" Driver "freedreno" VendorName "Freedreno " BoardName "SoC" EndSection But I am getting segmentaion fault and following is snippet of /var/log/Xorg.0.log [ 6587.058] (II) No msm DRM/KMS, fallback to fbdev/kgsl [ 6587.059] [ 6587.059] Backtrace: [ 6587.059] [ 6587.059] Segmentation fault at address 0x3 [ 6587.059] Fatal server error: [ 6587.059] Caught signal 11 (Segmentation fault). Server aborting Please let me know how I can go about debugging it well, IgnoreABI is more than a bit scary.. the old downstream msm fdbdev driver wasn't a bit non-standard, so there might be issues w/ xf86-video-freedreno working w/ a different fbdev driver (not to mention the non-KMS codepaths probably haven't been exercised in a while). But I suspect an ABI mismatch between xf86-video-freedreno is likely to cause more problems. BR, -R On Friday 14 July 2017 01:13 PM, abhijit naik wrote: Hi Ilia, Thank you very much for your reply. I am able to create msm_dri.so file with options you provided Even after that, soft pipe is being used for rendering. I am suspecting that glxinfo will use driver depending on _drv.so being detected by xinit Now I have freedreno_drv.so too. But still soft pipe is being used. I am trying to solve this puzzle. Warm Regards, Abhijit On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 You absolutely need --enable-dri. Gallium drivers are also DRI drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, while the others are "gallium" drivers. However they're all DRI drivers. You can build mesa --with-dri-drivers="" --with-gallium-drivers="freedreno", but you have to leave DRI(3) enabled. -ilia ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
> I guess that it is failing to find the old kgsl shim drm driver, which > enabled allocation of GEM buffers for pixmaps. I know Wladimir played > a bit with this on imx5, but I think he was just using gbm/kms and not > x11. I guess he was using imx-drm for GEM buffer allocation? Yes, for the a20x stuff I use the old GSL kernel driver (forward-ported to 4.12, see https://github.com/laanwj/linux-freedreno-a2xx). This creates a /dev/gsl_kmod, which has an interface different from the "newer" kgsl. And a mesa and libdrm that is patched to use this: https://github.com/laanwj/mesa-freedreno-a2xx https://github.com/laanwj/libdrm-freedreno-a20x This fork of mesa doesn't support X11, only kms/gbm-based rendering. All of this is very experimental. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Wladimir, Thank you very much for the reply. I am able to build the kernel, drm and mesa components. After loading the kernel, I am getting following entries, /dev/gsl_kmod /dev/dri/card0 /dev/dri/renderD128 Can you please let me know what are the test application that be used to test the driver through gsl_kmod interface? Now to test the driver, I am running kmscube, which is giving exception, "@MF@ using DRM kernel interface @MF@ fd_device_del refcnt=1 @MF@ fd_device_del_impl @MF@ fd_cleanup_bo_cache devtime=0 time=0 num_buckets=55 Segmentation fault" Can freedreno test be used with gsl_kmod interface, I am simultaneously trying build freedreno tests? I have allocated 9MB of memory to "memchunk" in drivers/mxc/amd-gpu/platform/hal/linux/gsl_hal.c as, dma_alloc_coherent is failing for 72MB Regards, Abhijit On Monday 07 August 2017 04:59 PM, Wladimir wrote: I guess that it is failing to find the old kgsl shim drm driver, which enabled allocation of GEM buffers for pixmaps. I know Wladimir played a bit with this on imx5, but I think he was just using gbm/kms and not x11. I guess he was using imx-drm for GEM buffer allocation? Yes, for the a20x stuff I use the old GSL kernel driver (forward-ported to 4.12, see https://github.com/laanwj/linux-freedreno-a2xx). This creates a /dev/gsl_kmod, which has an interface different from the "newer" kgsl. And a mesa and libdrm that is patched to use this: https://github.com/laanwj/mesa-freedreno-a2xx https://github.com/laanwj/libdrm-freedreno-a20x This fork of mesa doesn't support X11, only kms/gbm-based rendering. All of this is very experimental. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hello Abhijit, On Thu, Aug 10, 2017 at 07:45:03PM +0530, abhijit wrote: > Hi Wladimir, > > Thank you very much for the reply. > > I am able to build the kernel, drm and mesa components. > > After loading the kernel, I am getting following entries, > /dev/gsl_kmod > /dev/dri/card0 > /dev/dri/renderD128 > That's expected. gsl_kmod is for the GPU, card0/renderD128 is the i.mx5x IPU/scanout. > Can you please let me know what are the test application that be used to > test the driver through gsl_kmod interface? Anything using kms/gbm should work. > Now to test the driver, I am running kmscube, which is giving exception, > "@MF@ using DRM kernel interface >@MF@ fd_device_del refcnt=1 >@MF@ fd_device_del_impl >@MF@ fd_cleanup_bo_cache devtime=0 time=0 num_buckets=55 >Segmentation fault" you need: export FD_DRM_USE_KGSL=1 > Can freedreno test be used with gsl_kmod interface, I am simultaneously > trying build freedreno tests? I don't know. Might well be that they depend on a msm interface to the kernel. > I have allocated 9MB of memory to "memchunk" in > drivers/mxc/amd-gpu/platform/hal/linux/gsl_hal.c as, dma_alloc_coherent is > failing for 72MB I set CONFIG_CMA_SIZE_MBYTES=128 to avoid that issue. 9MB of video memory is not enough, in any case. and mmu is currently forced to disabled in the amdgpu driver as it resulted in crashes. (this is something that broke during forward-porting it from the 2.x to 3.x kernel, unfortunately) Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Wladimir, Thank you very much for your help. I am able to run kmscube application and able to notice substantial difference b/w H/W and S/W rendering. I also changed freedreno test-cube.c application with GBM interface and it also worked fine. Regards, Abhijit On Thursday 10 August 2017 07:59 PM, Wladimir J. van der Laan wrote: Hello Abhijit, On Thu, Aug 10, 2017 at 07:45:03PM +0530, abhijit wrote: Hi Wladimir, Thank you very much for the reply. I am able to build the kernel, drm and mesa components. After loading the kernel, I am getting following entries, /dev/gsl_kmod /dev/dri/card0 /dev/dri/renderD128 That's expected. gsl_kmod is for the GPU, card0/renderD128 is the i.mx5x IPU/scanout. Can you please let me know what are the test application that be used to test the driver through gsl_kmod interface? Anything using kms/gbm should work. Now to test the driver, I am running kmscube, which is giving exception, "@MF@ using DRM kernel interface @MF@ fd_device_del refcnt=1 @MF@ fd_device_del_impl @MF@ fd_cleanup_bo_cache devtime=0 time=0 num_buckets=55 Segmentation fault" you need: export FD_DRM_USE_KGSL=1 Can freedreno test be used with gsl_kmod interface, I am simultaneously trying build freedreno tests? I don't know. Might well be that they depend on a msm interface to the kernel. I have allocated 9MB of memory to "memchunk" in drivers/mxc/amd-gpu/platform/hal/linux/gsl_hal.c as, dma_alloc_coherent is failing for 72MB I set CONFIG_CMA_SIZE_MBYTES=128 to avoid that issue. 9MB of video memory is not enough, in any case. and mmu is currently forced to disabled in the amdgpu driver as it resulted in crashes. (this is something that broke during forward-porting it from the 2.x to 3.x kernel, unfortunately) Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi All, I am able to get the 3D graphic driver to run. Thank you very much for kind help. Now I am trying to run some 2D application from freedreno. I saw that these applications use libC2D2. I was able to get this library for UNIX, but I am not able to get libstlport for UNIX which is one of dependencies. I am concluding libC2D2 is specific to Andriod I am planning to use MonkVG and run tiger application that comes with Khronos so that I can use 3D renderer for 2D. I am falling back to OPEN GL ES 2.0, as OPENVG implementation is discontinued in Mesa Please let me know your inputs on this Regards, Abhijit On Monday 07 August 2017 02:41 PM, abhijit wrote: Hi Rob, Thank you very much for information. Actually I am not constrained to use X server. But can you please let me know what are the components that may be needed for testing freedreno test applications, apart from libdrm and mesa? I thought X may be needed for graphic drawing. Sorry if the questions are too basic. Actually I am getting overwhelmed with lot of options available and I am not getting what is the right way to proceed... I will try get something to work with GBM though Regards, Abhijit On Sunday 06 August 2017 04:32 PM, Rob Clark wrote: On Thu, Aug 3, 2017 at 8:23 AM, abhijit wrote: Hi All :) Finally I am able to get freedreno_drv.so and xserver ABI version to get matched. I am using buildroot to get the proper package dependency and build. Currently our target has following binaries, $(ROOT_DIR)/usr/lib/xorg/modules/drivers/freedreno_drv.so $(ROOT_DIR)/usr/lib/dri/msm_dri.so $(ROOT_DIR)/usr/lib/libdrm_freedreno.so I also loaded msm_kgsl_core.ko and msm_adreno.ko But my xinit is giving following output "[ 233.794] (WW) Falling back to old probe method for freedreno" "[ 233.831] (II) No msm DRM/KMS, fallback to fbdev/kgsl" I guess that it is failing to find the old kgsl shim drm driver, which enabled allocation of GEM buffers for pixmaps. I know Wladimir played a bit with this on imx5, but I think he was just using gbm/kms and not x11. I guess he was using imx-drm for GEM buffer allocation? BR, -R "[ 234.801] (II) UnloadModule: "freedreno"" "[ 234.801] (II) Unloading freedreno" Referring to freedreno architecture, I interpreted kgsl must be enabled in the libdrm and enabled same. But still freedreno module is getting unloaded I will be grateful if any body can give lead on this. Regards, Abhijit On Friday 14 July 2017 05:28 PM, Rob Clark wrote: On Fri, Jul 14, 2017 at 6:52 AM, abhijit wrote: Hi all, Running xinit load freedreno_drv.so file after adding configuration in /etc/X11/xorg.conf, Section "Server Flags" Option "IgnoreABI" EndSection Section "Device" Identifier "Device0" Driver "freedreno" VendorName "Freedreno " BoardName "SoC" EndSection But I am getting segmentaion fault and following is snippet of /var/log/Xorg.0.log [ 6587.058] (II) No msm DRM/KMS, fallback to fbdev/kgsl [ 6587.059] [ 6587.059] Backtrace: [ 6587.059] [ 6587.059] Segmentation fault at address 0x3 [ 6587.059] Fatal server error: [ 6587.059] Caught signal 11 (Segmentation fault). Server aborting Please let me know how I can go about debugging it well, IgnoreABI is more than a bit scary.. the old downstream msm fdbdev driver wasn't a bit non-standard, so there might be issues w/ xf86-video-freedreno working w/ a different fbdev driver (not to mention the non-KMS codepaths probably haven't been exercised in a while). But I suspect an ABI mismatch between xf86-video-freedreno is likely to cause more problems. BR, -R On Friday 14 July 2017 01:13 PM, abhijit naik wrote: Hi Ilia, Thank you very much for your reply. I am able to create msm_dri.so file with options you provided Even after that, soft pipe is being used for rendering. I am suspecting that glxinfo will use driver depending on _drv.so being detected by xinit Now I have freedreno_drv.so too. But still soft pipe is being used. I am trying to solve this puzzle. Warm Regards, Abhijit On 10-Jul-2017, at 8:25 PM, Ilia Mirkin wrote: On Mon, Jul 10, 2017 at 10:53 AM, abhijit wrote: Hi Rob, Thank you very much for your reply. I ensured that --enable-freedreno-kgsl is enabled in libdrm build and the same is copied to target The issue seems to be in mesa build I observed that there are two mechanism in which application can interact with underlaying DRM, 1. With DRI ($MESA_INSTALL_PATH/src/mesa/drivers/dri) 2. With Gallium driver ($MESA_INSTALL_PATH/src/gallium/drivers) Freedreno driver is present only in Case 2. For that reason I disabled dri in Mesa build and enabled gallium-xlib intreface, which will enable case 2 You absolutely need --enable-dri. Gallium drivers are also DRI drivers. The "src/mesa/drivers/dri" drivers are "classic" drivers, while the others are "gallium" drivers. However they're all DRI dr
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hello abhijit, > Now I am trying to run some 2D application from freedreno. I saw that these > applications use libC2D2. > > I was able to get this library for UNIX, but I am not able to get libstlport > for UNIX which is one of dependencies. I am concluding libC2D2 is specific > to Andriod You shouldn't need stlport for UNIX. As far as I remember it is a stand-alone implementation of the C++ standard library. Both clang and GCC have their own state-of-the-art C++ standard libraries readily available. > I am planning to use MonkVG and run tiger application that comes with > Khronos so that I can use 3D renderer for 2D. > > I am falling back to OPEN GL ES 2.0, as OPENVG implementation is > discontinued in Mesa I'm not sure what is the state of support for the 2D core, the Z160, in freedreno. I personally will likely not have time to look at that. Using the 3D hardware makes sense, however. For example the application I'm working on is also mostly a 2D application, it is built with Qt Quick, which uses OpenGL ES 2 as rendering backend. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi All, I have requirement to support OPENGL ES 2.0 in GPU hardware. But freedreno supports OPENGL 1.4. To support OPEN GL ES 2.0, I am planning to boot old linux kernel with binary only GPU driver and use reverse engineering tools. As I don't see any other option. But before I start, I wanted to confirm whether Open GL ES 2.0 based application can run with Open GL ES 1.4? My end goal is to use chromium browser on IMX537 based board. Please let me know your inputs. On Thu, Aug 17, 2017 at 4:04 PM, Wladimir J. van der Laan wrote: > Hello abhijit, > >> Now I am trying to run some 2D application from freedreno. I saw that these >> applications use libC2D2. >> >> I was able to get this library for UNIX, but I am not able to get libstlport >> for UNIX which is one of dependencies. I am concluding libC2D2 is specific >> to Andriod > > You shouldn't need stlport for UNIX. As far as I remember it is a stand-alone > implementation of the C++ standard library. Both clang and GCC have their > own state-of-the-art C++ standard libraries readily available. > >> I am planning to use MonkVG and run tiger application that comes with >> Khronos so that I can use 3D renderer for 2D. >> >> I am falling back to OPEN GL ES 2.0, as OPENVG implementation is >> discontinued in Mesa > > I'm not sure what is the state of support for the 2D core, the Z160, in > freedreno. I personally will likely not have time to look at that. > > Using the 3D hardware makes sense, however. For example the application I'm > working on is also mostly a 2D application, it is built with Qt Quick, which > uses OpenGL ES 2 as rendering backend. > > Regards, > Wladimir -- Best wishes, Abhijit Naik ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
mesa/freedreno supports gles as well as gl.. perhaps you built mesa without --enable-gles2? BR, -R On Fri, Sep 8, 2017 at 2:50 AM, abhijit naik wrote: > Hi All, > > I have requirement to support OPENGL ES 2.0 in GPU hardware. > > But freedreno supports OPENGL 1.4. To support OPEN GL ES 2.0, I am > planning to boot old linux kernel with binary only GPU driver and use > reverse engineering tools. As I don't see any other option. > > But before I start, I wanted to confirm whether Open GL ES 2.0 based > application can run with Open GL ES 1.4? > > My end goal is to use chromium browser on IMX537 based board. > > Please let me know your inputs. > > On Thu, Aug 17, 2017 at 4:04 PM, Wladimir J. van der Laan > wrote: >> Hello abhijit, >> >>> Now I am trying to run some 2D application from freedreno. I saw that these >>> applications use libC2D2. >>> >>> I was able to get this library for UNIX, but I am not able to get libstlport >>> for UNIX which is one of dependencies. I am concluding libC2D2 is specific >>> to Andriod >> >> You shouldn't need stlport for UNIX. As far as I remember it is a stand-alone >> implementation of the C++ standard library. Both clang and GCC have their >> own state-of-the-art C++ standard libraries readily available. >> >>> I am planning to use MonkVG and run tiger application that comes with >>> Khronos so that I can use 3D renderer for 2D. >>> >>> I am falling back to OPEN GL ES 2.0, as OPENVG implementation is >>> discontinued in Mesa >> >> I'm not sure what is the state of support for the 2D core, the Z160, in >> freedreno. I personally will likely not have time to look at that. >> >> Using the 3D hardware makes sense, however. For example the application I'm >> working on is also mostly a 2D application, it is built with Qt Quick, which >> uses OpenGL ES 2 as rendering backend. >> >> Regards, >> Wladimir > > > > -- > Best wishes, > Abhijit Naik ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Wladimir, I am facing issues while getting freedreno driver to work on imx53 based tx53 board from Karo I have earlier verified that A200 driver works for imx53 based QSRB board from Freescale. However for tx53 board, register read for getting chip ID is returning zero. Interestingly for both boards, dtsi is common, i.e imx53.dtsi.This dtsi contains, Clock information for CPU GPU device tree node Clock rates for both boards as below, kgsl_clock:gpu_clk 2 kgsl_clock:garb_clk 4 Following are output of /dev/cpuinfo for both boards QSRB(IMX): processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS: 66.66 Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part: 0xc08 CPU revision: 5 Hardware: Freescale i.MX53 (Device Tree Support) Revision: Serial : TX53(Karo): processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS: 40.00 Features: half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part: 0xc08 CPU revision: 5 Hardware: Freescale i.MX53 (Device Tree Support) Revision: Serial : Can you please guide me how I can debug this issue or you have faced similar issues when you were developing the driver? From output of cpuinfo, I see that only BogoMIPS is different for both CPUs, can this be an issue? Regards, Abhijit On Friday 08 September 2017 03:46 PM, Rob Clark wrote: mesa/freedreno supports gles as well as gl.. perhaps you built mesa without --enable-gles2? BR, -R On Fri, Sep 8, 2017 at 2:50 AM, abhijit naik wrote: Hi All, I have requirement to support OPENGL ES 2.0 in GPU hardware. But freedreno supports OPENGL 1.4. To support OPEN GL ES 2.0, I am planning to boot old linux kernel with binary only GPU driver and use reverse engineering tools. As I don't see any other option. But before I start, I wanted to confirm whether Open GL ES 2.0 based application can run with Open GL ES 1.4? My end goal is to use chromium browser on IMX537 based board. Please let me know your inputs. On Thu, Aug 17, 2017 at 4:04 PM, Wladimir J. van der Laan wrote: Hello abhijit, Now I am trying to run some 2D application from freedreno. I saw that these applications use libC2D2. I was able to get this library for UNIX, but I am not able to get libstlport for UNIX which is one of dependencies. I am concluding libC2D2 is specific to Andriod You shouldn't need stlport for UNIX. As far as I remember it is a stand-alone implementation of the C++ standard library. Both clang and GCC have their own state-of-the-art C++ standard libraries readily available. I am planning to use MonkVG and run tiger application that comes with Khronos so that I can use 3D renderer for 2D. I am falling back to OPEN GL ES 2.0, as OPENVG implementation is discontinued in Mesa I'm not sure what is the state of support for the 2D core, the Z160, in freedreno. I personally will likely not have time to look at that. Using the 3D hardware makes sense, however. For example the application I'm working on is also mostly a 2D application, it is built with Qt Quick, which uses OpenGL ES 2 as rendering backend. Regards, Wladimir -- Best wishes, Abhijit Naik ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi All, One more observation is, for TX53, uboot is enabling L2 cache "Enabling L2 Cache .." but for QSRB it is not showing such message. Please let me know if this can make difference. Which I think is unlikely :) Thank you for your help Regards, Abhijit On Friday 10 November 2017 05:16 PM, abhijit wrote: Hi Wladimir, I am facing issues while getting freedreno driver to work on imx53 based tx53 board from Karo I have earlier verified that A200 driver works for imx53 based QSRB board from Freescale. However for tx53 board, register read for getting chip ID is returning zero. Interestingly for both boards, dtsi is common, i.e imx53.dtsi.This dtsi contains, Clock information for CPU GPU device tree node Clock rates for both boards as below, kgsl_clock:gpu_clk 2 kgsl_clock:garb_clk 4 Following are output of /dev/cpuinfo for both boards QSRB(IMX): processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 66.66 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc08 CPU revision : 5 Hardware : Freescale i.MX53 (Device Tree Support) Revision : Serial : TX53(Karo): processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 40.00 Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc08 CPU revision : 5 Hardware : Freescale i.MX53 (Device Tree Support) Revision : Serial : Can you please guide me how I can debug this issue or you have faced similar issues when you were developing the driver? From output of cpuinfo, I see that only BogoMIPS is different for both CPUs, can this be an issue? Regards, Abhijit On Friday 08 September 2017 03:46 PM, Rob Clark wrote: mesa/freedreno supports gles as well as gl.. perhaps you built mesa without --enable-gles2? BR, -R On Fri, Sep 8, 2017 at 2:50 AM, abhijit naik wrote: Hi All, I have requirement to support OPENGL ES 2.0 in GPU hardware. But freedreno supports OPENGL 1.4. To support OPEN GL ES 2.0, I am planning to boot old linux kernel with binary only GPU driver and use reverse engineering tools. As I don't see any other option. But before I start, I wanted to confirm whether Open GL ES 2.0 based application can run with Open GL ES 1.4? My end goal is to use chromium browser on IMX537 based board. Please let me know your inputs. On Thu, Aug 17, 2017 at 4:04 PM, Wladimir J. van der Laan wrote: Hello abhijit, Now I am trying to run some 2D application from freedreno. I saw that these applications use libC2D2. I was able to get this library for UNIX, but I am not able to get libstlport for UNIX which is one of dependencies. I am concluding libC2D2 is specific to Andriod You shouldn't need stlport for UNIX. As far as I remember it is a stand-alone implementation of the C++ standard library. Both clang and GCC have their own state-of-the-art C++ standard libraries readily available. I am planning to use MonkVG and run tiger application that comes with Khronos so that I can use 3D renderer for 2D. I am falling back to OPEN GL ES 2.0, as OPENVG implementation is discontinued in Mesa I'm not sure what is the state of support for the 2D core, the Z160, in freedreno. I personally will likely not have time to look at that. Using the 3D hardware makes sense, however. For example the application I'm working on is also mostly a 2D application, it is built with Qt Quick, which uses OpenGL ES 2 as rendering backend. Regards, Wladimir -- Best wishes, Abhijit Naik ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
On Thu, Nov 16, 2017 at 7:00 AM, abhijit wrote: > Hi All, > > One more observation is, for TX53, uboot is enabling L2 cache "Enabling L2 > Cache .." but for QSRB it is not showing such message. > > Please let me know if this can make difference. Which I think is unlikely :) If the registers of the GPU return 0, it's likely that either the base address in the dts is not correct, or the device is not powered on / clocked properly. If there is a kernel available for your device that does successfully enables the GPU you could maybe compare. Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Wladimir, Thank you very much for you response. I am using the kernel which is provided by you and I was able to successfully get the GPU driver on to imx53 based QSRB board. I am using the same kernel for imx53 based tx53 board from karo, but I am having issue with getting GPU ID Interestingly imx53.dtsi is common for both imx53-tx53-x13x.dts and imx53-qsrb.dts. imx53.dtsi contains DTS entries for GPU and clocks. I verified that clock values are same for both qsrb and tx53. Only thing I have to verify is if GPU completely powered on. Can you please let me know how to ensure this? Regards, Abhijit On Thursday 16 November 2017 11:30 AM, abhijit wrote: Hi All, One more observation is, for TX53, uboot is enabling L2 cache "Enabling L2 Cache .." but for QSRB it is not showing such message. Please let me know if this can make difference. Which I think is unlikely :) Thank you for your help Regards, Abhijit On Friday 10 November 2017 05:16 PM, abhijit wrote: Hi Wladimir, I am facing issues while getting freedreno driver to work on imx53 based tx53 board from Karo I have earlier verified that A200 driver works for imx53 based QSRB board from Freescale. However for tx53 board, register read for getting chip ID is returning zero. Interestingly for both boards, dtsi is common, i.e imx53.dtsi.This dtsi contains, Clock information for CPU GPU device tree node Clock rates for both boards as below, kgsl_clock:gpu_clk 2 kgsl_clock:garb_clk 4 Following are output of /dev/cpuinfo for both boards QSRB(IMX): processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 66.66 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc08 CPU revision : 5 Hardware : Freescale i.MX53 (Device Tree Support) Revision : Serial : TX53(Karo): processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 40.00 Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x2 CPU part : 0xc08 CPU revision : 5 Hardware : Freescale i.MX53 (Device Tree Support) Revision : Serial : Can you please guide me how I can debug this issue or you have faced similar issues when you were developing the driver? From output of cpuinfo, I see that only BogoMIPS is different for both CPUs, can this be an issue? Regards, Abhijit On Friday 08 September 2017 03:46 PM, Rob Clark wrote: mesa/freedreno supports gles as well as gl.. perhaps you built mesa without --enable-gles2? BR, -R On Fri, Sep 8, 2017 at 2:50 AM, abhijit naik wrote: Hi All, I have requirement to support OPENGL ES 2.0 in GPU hardware. But freedreno supports OPENGL 1.4. To support OPEN GL ES 2.0, I am planning to boot old linux kernel with binary only GPU driver and use reverse engineering tools. As I don't see any other option. But before I start, I wanted to confirm whether Open GL ES 2.0 based application can run with Open GL ES 1.4? My end goal is to use chromium browser on IMX537 based board. Please let me know your inputs. On Thu, Aug 17, 2017 at 4:04 PM, Wladimir J. van der Laan wrote: Hello abhijit, Now I am trying to run some 2D application from freedreno. I saw that these applications use libC2D2. I was able to get this library for UNIX, but I am not able to get libstlport for UNIX which is one of dependencies. I am concluding libC2D2 is specific to Andriod You shouldn't need stlport for UNIX. As far as I remember it is a stand-alone implementation of the C++ standard library. Both clang and GCC have their own state-of-the-art C++ standard libraries readily available. I am planning to use MonkVG and run tiger application that comes with Khronos so that I can use 3D renderer for 2D. I am falling back to OPEN GL ES 2.0, as OPENVG implementation is discontinued in Mesa I'm not sure what is the state of support for the 2D core, the Z160, in freedreno. I personally will likely not have time to look at that. Using the 3D hardware makes sense, however. For example the application I'm working on is also mostly a 2D application, it is built with Qt Quick, which uses OpenGL ES 2 as rendering backend. Regards, Wladimir -- Best wishes, Abhijit Naik ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hello abhijit, On Thu, Nov 16, 2017 at 01:02:21PM +0530, abhijit wrote: > Hi Wladimir, > > Thank you very much for you response. > > I am using the kernel which is provided by you and I was able to > successfully get the GPU driver on to imx53 based QSRB board. > > I am using the same kernel for imx53 based tx53 board from karo, but I am > having issue with getting GPU ID > > Interestingly imx53.dtsi is common for both imx53-tx53-x13x.dts and > imx53-qsrb.dts. > > imx53.dtsi contains DTS entries for GPU and clocks. > > I verified that clock values are same for both qsrb and tx53. Only thing I > have to verify is if GPU completely powered on. Can you please let me know > how to ensure this? Unfortunately I don't know, I've never been involved in that side of board bringup, I just write (mostly user space) graphics drivers. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi all, @Wladimir, Thank you very much for you kind response. I am planning to boot older version of linux kernel(2.6) on Karo board and use reverse engineering tools to get any GPU related settings. Please let me know what are the important settings I have to look into, that may be useful to address the issue of GPU chip ID becoming zero. Regards, Abhijit On Thursday 16 November 2017 03:42 PM, Wladimir J. van der Laan wrote: Hello abhijit, On Thu, Nov 16, 2017 at 01:02:21PM +0530, abhijit wrote: Hi Wladimir, Thank you very much for you response. I am using the kernel which is provided by you and I was able to successfully get the GPU driver on to imx53 based QSRB board. I am using the same kernel for imx53 based tx53 board from karo, but I am having issue with getting GPU ID Interestingly imx53.dtsi is common for both imx53-tx53-x13x.dts and imx53-qsrb.dts. imx53.dtsi contains DTS entries for GPU and clocks. I verified that clock values are same for both qsrb and tx53. Only thing I have to verify is if GPU completely powered on. Can you please let me know how to ensure this? Unfortunately I don't know, I've never been involved in that side of board bringup, I just write (mostly user space) graphics drivers. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi All, Just to update, Karo doesn't have support 2.6.35 Linux Kernel However I observed that even w.r.t u-boot, tx53 based board returns zero as GPU ID and QSRB board returns proper GPU ID Regards, Abhijit On Friday 24 November 2017 10:43 AM, abhijit wrote: Hi all, @Wladimir, Thank you very much for you kind response. I am planning to boot older version of linux kernel(2.6) on Karo board and use reverse engineering tools to get any GPU related settings. Please let me know what are the important settings I have to look into, that may be useful to address the issue of GPU chip ID becoming zero. Regards, Abhijit On Thursday 16 November 2017 03:42 PM, Wladimir J. van der Laan wrote: Hello abhijit, On Thu, Nov 16, 2017 at 01:02:21PM +0530, abhijit wrote: Hi Wladimir, Thank you very much for you response. I am using the kernel which is provided by you and I was able to successfully get the GPU driver on to imx53 based QSRB board. I am using the same kernel for imx53 based tx53 board from karo, but I am having issue with getting GPU ID Interestingly imx53.dtsi is common for both imx53-tx53-x13x.dts and imx53-qsrb.dts. imx53.dtsi contains DTS entries for GPU and clocks. I verified that clock values are same for both qsrb and tx53. Only thing I have to verify is if GPU completely powered on. Can you please let me know how to ensure this? Unfortunately I don't know, I've never been involved in that side of board bringup, I just write (mostly user space) graphics drivers. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi All, This is to inform that we managed to get the 3D driver working on Karo board The issue was with u-boot. In u-boot code of Karo, CCM_CMEOR.MOD_EN_OV_GPU was set to 0 CCM_CCGR5.gpu_clk_enable was set to 0 After changing above register bits to one, I am able to get GPU ID Thank you very much for your help On Monday 11 December 2017 05:07 PM, abhijit wrote: Hi All, Just to update, Karo doesn't have support 2.6.35 Linux Kernel However I observed that even w.r.t u-boot, tx53 based board returns zero as GPU ID and QSRB board returns proper GPU ID Regards, Abhijit On Friday 24 November 2017 10:43 AM, abhijit wrote: Hi all, @Wladimir, Thank you very much for you kind response. I am planning to boot older version of linux kernel(2.6) on Karo board and use reverse engineering tools to get any GPU related settings. Please let me know what are the important settings I have to look into, that may be useful to address the issue of GPU chip ID becoming zero. Regards, Abhijit On Thursday 16 November 2017 03:42 PM, Wladimir J. van der Laan wrote: Hello abhijit, On Thu, Nov 16, 2017 at 01:02:21PM +0530, abhijit wrote: Hi Wladimir, Thank you very much for you response. I am using the kernel which is provided by you and I was able to successfully get the GPU driver on to imx53 based QSRB board. I am using the same kernel for imx53 based tx53 board from karo, but I am having issue with getting GPU ID Interestingly imx53.dtsi is common for both imx53-tx53-x13x.dts and imx53-qsrb.dts. imx53.dtsi contains DTS entries for GPU and clocks. I verified that clock values are same for both qsrb and tx53. Only thing I have to verify is if GPU completely powered on. Can you please let me know how to ensure this? Unfortunately I don't know, I've never been involved in that side of board bringup, I just write (mostly user space) graphics drivers. Regards, Wladimir ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Waldimir, Hi Wladimir, Can you please let me know if you have any plans to make changes for A200 mainline? I have ported the KGSL driver along with other source files to 4.14.1 kernel and got it working. Can you let me know, if I can commit the code to your repository? Regards, Abhijit On Monday 07 August 2017 04:59 PM, Wladimir wrote: I guess that it is failing to find the old kgsl shim drm driver, which enabled allocation of GEM buffers for pixmaps. I know Wladimir played a bit with this on imx5, but I think he was just using gbm/kms and not x11. I guess he was using imx-drm for GEM buffer allocation? Yes, for the a20x stuff I use the old GSL kernel driver (forward-ported to 4.12, see https://github.com/laanwj/linux-freedreno-a2xx). This creates a /dev/gsl_kmod, which has an interface different from the "newer" kgsl. And a mesa and libdrm that is patched to use this: https://github.com/laanwj/mesa-freedreno-a2xx https://github.com/laanwj/libdrm-freedreno-a20x This fork of mesa doesn't support X11, only kms/gbm-based rendering. All of this is very experimental. Regards, Wladimir . ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi Abhijit, Looks like there may have been some duplication of effort... https://github.com/laanwj/linux-freedreno-a2xx/commits/4.15-rc5-rdu1-kgsl Seems to be based on 4.15 if the branch name is to be believed. -ilia On Fri, Mar 16, 2018 at 8:54 AM, abhijit wrote: > Hi Waldimir, > > Hi Wladimir, > > Can you please let me know if you have any plans to make changes for A200 > mainline? > > I have ported the KGSL driver along with other source files to 4.14.1 kernel > and got it working. Can you let me know, if I can commit the code to your > repository? > > Regards, >Abhijit > > On Monday 07 August 2017 04:59 PM, Wladimir wrote: >>> >>> I guess that it is failing to find the old kgsl shim drm driver, which >>> enabled allocation of GEM buffers for pixmaps. I know Wladimir played >>> a bit with this on imx5, but I think he was just using gbm/kms and not >>> x11. I guess he was using imx-drm for GEM buffer allocation? >> >> >> Yes, for the a20x stuff I use the old GSL kernel driver >> (forward-ported to 4.12, see >> https://github.com/laanwj/linux-freedreno-a2xx). >> This creates a /dev/gsl_kmod, which has an interface different from >> the "newer" kgsl. >> >> And a mesa and libdrm that is patched to use this: >> >> https://github.com/laanwj/mesa-freedreno-a2xx >> https://github.com/laanwj/libdrm-freedreno-a20x >> >> This fork of mesa doesn't support X11, only kms/gbm-based rendering. >> All of this is very experimental. >> >> Regards, >> Wladimir >> . >> > ___ > Freedreno mailing list > Freedreno@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/freedreno ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
Re: [Freedreno] Whether A200 driver is supported by Linux Mainline Kernel
Hi ilia, Thank you very much for information. On Friday 16 March 2018 08:45 PM, Ilia Mirkin wrote: Hi Abhijit, Looks like there may have been some duplication of effort... https://github.com/laanwj/linux-freedreno-a2xx/commits/4.15-rc5-rdu1-kgsl Seems to be based on 4.15 if the branch name is to be believed. -ilia On Fri, Mar 16, 2018 at 8:54 AM, abhijit wrote: Hi Waldimir, Hi Wladimir, Can you please let me know if you have any plans to make changes for A200 mainline? I have ported the KGSL driver along with other source files to 4.14.1 kernel and got it working. Can you let me know, if I can commit the code to your repository? Regards, Abhijit On Monday 07 August 2017 04:59 PM, Wladimir wrote: I guess that it is failing to find the old kgsl shim drm driver, which enabled allocation of GEM buffers for pixmaps. I know Wladimir played a bit with this on imx5, but I think he was just using gbm/kms and not x11. I guess he was using imx-drm for GEM buffer allocation? Yes, for the a20x stuff I use the old GSL kernel driver (forward-ported to 4.12, see https://github.com/laanwj/linux-freedreno-a2xx). This creates a /dev/gsl_kmod, which has an interface different from the "newer" kgsl. And a mesa and libdrm that is patched to use this: https://github.com/laanwj/mesa-freedreno-a2xx https://github.com/laanwj/libdrm-freedreno-a20x This fork of mesa doesn't support X11, only kms/gbm-based rendering. All of this is very experimental. Regards, Wladimir . ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno ___ Freedreno mailing list Freedreno@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/freedreno
