Skip to contentSkip to conversation

sunxi mali binary driver

DISCUSSION Trevor Woerner 2 participants 3 messages Sep 22, 2015

lore
Share & tools
lore
#0 lore raw

Hello,

I'm trying to build an image for my cubietruck that uses the binary accelerated mali driver (sunxi-mali) and have a couple questions.

It was my impression that the binary user-space libraries (sunxi-mali?) only work with specific versions of the kernel.

By default the cubietruck machine definition will try to build the upstream kernel, but by default it also sets the preferred providers of egl, gles1, and gles2 to sunxi-mali. Wouldn't that cause problems? If I want to use the accelerated, binary mali driver, don't I have to stick with the sunxi kernel (3.4.90) too?

Best regards,
Trevor

#1 lore raw

2015-09-22 19:27 GMT+02:00 Trevor Woerner <[email protected]>:

Quoted 2 lines

Hello,

Hi Trevor,

Quoted 6 lines

I'm trying to build an image for my cubietruck that uses the binary accelerated mali driver (sunxi-mali) and have a couple questions.

It was my impression that the binary user-space libraries (sunxi-mali?) only work with specific versions of the kernel.

sunxi-mali binary driver build by this recipe
(https://github.com/linux-sunxi/meta-sunxi/blob/master/recipes-graphics/libgles/sunxi-mali_git.bb)
only works with 3.4 kernel.
You can find some informations about sunxi-mali here :
http://linux-sunxi.org/Mali_binary_driver

The problem is that linux-sunxi 3.4.x kernel contains mali r3p0 driver
(https://github.com/linux-sunxi/linux-sunxi/tree/sunxi-3.4/drivers/gpu/mali)
where linux mainline doesn't.

Quoted 6 lines

By default the cubietruck machine definition will try to build the upstream kernel, but by default it also sets the preferred providers of egl, gles1, and gles2 to sunxi-mali. Wouldn't that cause problems? If I want to use the accelerated, binary mali driver, don't I have to stick with the sunxi kernel (3.4.90) too?

We could maybe avoid the build of sunxi-mali recipe when a mainline kernel is built.

Quoted 2 lines

Best regards,
Trevor

Best Regards,
Nicolas

Signature · 4 lines
Nicolas Aguirre
Mail: [email protected]
Web: http://www.calaos.fr
Blog: http://dev.enlightenment.fr/~captainigloo/
#2 lore raw

Hi Nicolas,

Quoted 17 lines · Nicolas Aguirre

2015-09-22 19:27 GMT+02:00 Trevor Woerner <[email protected]>:

Quoted 2 lines

Hello,

Hi Trevor,

Quoted 6 lines

I'm trying to build an image for my cubietruck that uses the binary accelerated mali driver (sunxi-mali) and have a couple questions.

It was my impression that the binary user-space libraries (sunxi-mali?) only work with specific versions of the kernel.

sunxi-mali binary driver build by this recipe
(https://github.com/linux-sunxi/meta-sunxi/blob/master/recipes-graphics/libgles/sunxi-mali_git.bb)
only works with 3.4 kernel.
You can find some informations about sunxi-mali here :
http://linux-sunxi.org/Mali_binary_driver

Quoted 3 lines

The problem is that linux-sunxi 3.4.x kernel contains mali r3p0 driver
(https://github.com/linux-sunxi/linux-sunxi/tree/sunxi-3.4/drivers/gpu/mali)
where linux mainline doesn't.

Thank you for the clarification! That's what I thought, but the fact the binary was being included with the mainline had me confused :-)

Quoted 8 lines
Quoted 6 lines

By default the cubietruck machine definition will try to build the upstream kernel, but by default it also sets the preferred providers of egl, gles1, and gles2 to sunxi-mali. Wouldn't that cause problems? If I want to use the accelerated, binary mali driver, don't I have to stick with the sunxi kernel (3.4.90) too?

We could maybe avoid the build of sunxi-mali recipe when a mainline kernel is built.

Ok, I could take a look at that too.

Best regards,
Trevor