Hi Jerome,

This is a known issue but a bug was not opened on this one. This is the caused by the below commit:
https://github.com/96boards/linux/pull/118

A fix for this is being worked on.  You can try it:
diff --git a/arch/arm64/boot/dts/hi6220.dtsi b/arch/arm64/boot/dts/hi6220.dtsi
index 7ffdc2b..17c0f86 100644
--- a/arch/arm64/boot/dts/hi6220.dtsi
+++ b/arch/arm64/boot/dts/hi6220.dtsi
@@ -993,7 +993,6 @@
  mali:mali@f4080000 {
  compatible = "arm,mali-450", "arm,mali-utgard";
  reg = <0x0 0x3f100000 0x0 0x00708000>;
- dma-coherent;
  clocks = <&clock_media HI6220_G3D_CLK>,
  <&clock_media HI6220_G3D_PCLK>;
  clock-names = "clk_g3d", "pclk_g3d";
-- 
1.9.1




On 15 October 2015 at 18:52, Jerome Forissier <jerome.forissier@linaro.org> wrote:
Hi,

I am trying AOSP snapshot 184 [1] + UEFI snapshot 75 [2] on my HiKey board, and I'm seeing some corruption on the HDMI display [3]. OpenGLRenderer logs some 'Out of memory' errors.

Am I doing something wrong? Is this a known issue? (I found nothing in the bug tracker [4]).

I have posted the outputs of 'adbg logcat' [5] and 'adbg shell dmesg' [6], taken shortly after a clean boot.


Thanks,
-- 
Jerome


_______________________________________________
Dev mailing list
Dev@lists.96boards.org
https://lists.96boards.org/mailman/listinfo/dev