Hi;
I buy a odroid-c1(the cpu is amlogic s805) which the GPU is Mali-450 MP4 and the os is ubuntu .I port the Mali driver on the Amlogic s802 which the GPU is Mali-450 MP6 and I run the Ubuntu os. The s802 can setup normally. The display is ok.But,When I run the glmark-es2 od kodi in the ubuntu which can run nomal on s805 (odroid),the display have nothing and the program exit automatically.
The serial output :
[ 38.726301@1] Mali<2>: Session started
[ 38.786947@3] efuse version is not selected.efuse_getinfo_byID
[ 38.947359@3] UMP<2>: Session closed
[ 38.947676@3] Mali<2>: Session has ended
Now I can not determine where the problem lies,anyone can help me? Thanks
Hi liuyongli,
When you say you port the Mali driver from the S802 to the S805, can you be more specific?
Are you talking about the kernel side, userspace side, or both parts of the Mali driver?
The driver requires integration into the given SoC, which is done by the vendor, Amlogic in this instance. Although both SoC's are from Amlogic, it is unlikely that the integration will be the same for the two SoC's as they contain not only different Mali-450's but different CPUs too, and probably many other differences.
When you say the display is ok, that could be because 2D blitting is usually done in a dedicated 2D hardware block, not the Mali GPU (Although if the environment uses OpenGL ES then it would be using Mali - can you confirm what the environment is using as its graphics API?) and as such, changing the Mali driver will have no effect on this 2D environment.
Running any OpenGL ES based application will certainly make use of the Mali and it sounds like it is these kind of applications that are failing for you, which makes sense if the integration is broken.
As I have mentioned above, the integration is handled by the vendor, so if this is indeed the issue at hand, you would need to contact Amlogic to resolve this issue.
Kind Regards,
Michael McGeagh
hello
I'd like to understand exactly what is blocking?
if the problem is due to a lack of definition of eFuse: EFUSE_SOC_CHIP_M8BABY (for ODROID C1)
Or If the problem comes from Mali driver, what do you use : a mali-x11 version or a Mali-fbdev ?
I met some problems and were resolved with switching from one to the other.
Hello;
Thank you for reply.
I got the android SDK for s802 from the amlogic .And the android can run normally and the GPU can work perfeck.Now I want to run the ubuntu on the s802.I found the ODROID-C1(s805)which run the ubuntu when I google.So I download the kernel sourcecode of s805 ,and I build the kenrel with the default config except the Meson SOC which I select the Meson8 series.
I flash the uImage and run the ubuntu os which can work on s805 .The os can setup normally and the display is ok .But the Mali can not work.
the kernel setup log :
[drm] Initialized drm 1.1.0 20060810
[ 2.319810@0] Mali<2>: Inserting Mali v401 device driver.
[ 2.324398@0] Mali<2>: Compiled: Mar 30 2015, time: 10:08:53.
[ 2.330101@0] Mali<2>: Driver revision: -v3.10.59-689-gb33daad
[ 2.335920@0] Mali<2>: mali_module_init() registering device
[ 2.341715@0] gpu cooling register okay with err=0
[ 2.346379@0] gpu core cooling register okay with err=0
[ 2.351512@0] Mali<2>: mali_module_init() registering driver
[ 2.357266@0] Mali<2>: mali_probe(): Called for platform device mali-utgard
[ 2.364200@0] Mali<2>: Using device defined memory settings (dedicated: 0x00000000@0x00000000, shared: 0x40000000)
[ 2.374410@0] Mali<2>: Using device defined frame buffer settings (0x00000000@0x00000000)
[ 2.382564@0] Mali<2>: Mali PMU: Creating Mali PMU core
[ 2.387745@0] Mali<2>: Mali PMU: mask 0xf, pp_core 8, l2_core 3
[ 2.393940@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
[ 2.399620@0] Mali<2>: Mali PP: Base address of PP core: 0xd00c8000
[ 2.405912@0] Mali<2>: Found Mali GPU Mali-450 MP r0p0
[ 2.410977@0] Mali<2>: Mali PM domain: Creating Mali PM domain (mask=0x00000001)
[ 2.418358@0] Mali<2>: Mali PM domain: Creating Mali PM domain (mask=0x00000002)
[ 2.425723@0] Mali<2>: Mali PM domain: Creating Mali PM domain (mask=0x00000004)
[ 2.433080@0] Mali<2>: Mali PM domain: Creating Mali PM domain (mask=0x00000008)
[ 2.441729@0] Mali<2>: Mali DLBU: Initializing
[ 2.445023@0] Mali<2>: Mali DMA: Created Mali APB DMA unit
[ 2.450333@0] Mali<2>: Mali L2 cache: Created Mali_L2: 8K, 4-way, 64byte cache line, 128bit external bus
[ 2.459973@0] Mali<2>: Mali L2 cache: Created Mali_L2: 128K, 4-way, 64byte cache line, 128bit external bus
[ 2.469589@0] Mali<2>: Mali L2 cache: Created Mali_L2: 128K, 4-way, 64byte cache line, 128bit external bus
[ 2.479229@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_GP_MMU
[ 2.485123@0] Mali<2>: Mali GP: Creating Mali GP core: Mali_GP
[ 2.490922@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP0_MMU
[ 2.496906@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
[ 2.502778@0] Mali<2>: Mali PP: Base address of PP core: 0xd00c8000
[ 2.509035@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP1_MMU
[ 2.515021@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP1
[ 2.520895@0] Mali<2>: Mali PP: Base address of PP core: 0xd00ca000
[ 2.527185@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP2_MMU
[ 2.533125@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP2
[ 2.539005@0] Mali<2>: Mali PP: Base address of PP core: 0xd00cc000
[ 2.545277@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP3_MMU
[ 2.551241@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP3
[ 2.557134@0] Mali<2>: Mali PP: Base address of PP core: 0xd00e8000
[ 2.563391@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP4_MMU
[ 2.569359@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP4
[ 2.575250@0] Mali<2>: Mali PP: Base address of PP core: 0xd00ea000
[ 2.581507@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP5_MMU
[ 2.587487@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP5
[ 2.593355@0] Mali<2>: Mali PP: Base address of PP core: 0xd00ec000
[ 2.599616@0] Mali<2>: Starting new virtual group for MMU PP broadcast core Mali_PP_MMU_Broadcast
[ 2.608450@0] Mali<2>: Mali DLBU: Creating Mali dynamic load balancing unit: Mali_DLBU
[ 2.616339@0] Mali<2>: Mali Broadcast unit: Creating Mali Broadcast unit: Mali_Broadcast
[ 2.624408@0] Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP_MMU_Broadcast
[ 2.631150@0] Mali<2>: Mali PP: Creating Mali PP core: Mali_PP_Broadcast
[ 2.637834@0] Mali<2>: Mali PP: Base address of PP core: 0xd00d6000
[ 2.644091@0] Mali<2>: 3+3 PP cores initialized
[ 2.648602@0] Mali<2>: Mali GPU Utilization: Platform has it's own policy
[ 2.655430@0] Mali<2>: Mali GPU Utilization: Utilization handler installed with interval 300
[ 2.664598@0] Mali<2>: mali_probe(): Successfully initialized driver for platform device mali-utgard
[ 2.672993@0] Mali: Mali device driver loaded
[ 2.677304@0] UMP<2>: Inserting UMP device driver. Compiled: Mar 30 2015, time: 10:09:12
[ 2.685504@0] UMP<2>: Using OS memory backend, allocation limit: 268435456
[ 2.692174@0] UMP: UMP device driver 0000 loaded
From the message I think the mali init is ok .I use the libMali.so and libump.so in the ubuntu os which work fine on s805 .The glmark-es2 run failed .I have no idea why the glmark-es2 exit automatically.
I port the Mali driver from the android SDK to ubuntu for s802 .The problem as .
The android and ubuntu use the same mali driver (kernel side),the difference is userspace .So I complile the libmali.so or libump.so again ？ the libmali.so close ?
Hi
If you are running under Ubuntu, i suggest you to install odroid-utility
~:sudo
sudo
#:wget -O /usr/local/bin/odroid-utility.sh https://raw.githubusercontent.com/mdrjr/odroid-utility/master/odroid-utility.sh#:chmod +x /usr/local/bin/odroid-utility.sh#:odroid-utility.sh
And run the update for Mali DDX, that will correct this probleme i mean.
Regards
hello;
Thank you first.
I also doubt that .But,When I disable CONFIG_GPU_THERMAL ,The efuse version is not selected.efuse_getinfo_byID missing .So I`m not sure whether this reason .
I do not known the difference between mali-x11 and Mali-fbdev . I can google and have a try. Thank you .
hi;
Thank you I have a try .But is not the same as the CPU It doesn't matter ?
odroid can support odroid-c1（s805），now I use the s802.
Ok
I mean it is a kernel module problem.
S802 using meson8 and S805 using meson8b
You may will have to rebuild your kernel for use it correctly
in particular if now you're not on a Hardkenel soc (they have clearly modify the original code)
I used mali-x11 instead of the mali-fbdev .but the glmark2-es2 failed . can you teach me how to change them ? Thank you