New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable CMA back for sun7i kernel #744

Closed
iavael opened this Issue Aug 26, 2017 · 7 comments

Comments

Projects
None yet
3 participants
@iavael

iavael commented Aug 26, 2017

Can you enable CMA back, please, so that usage of libump won't cause kernel oops and Xorg crash? I see, that patch with CMA-enabled UMP is applied, but CONFIG_CMA is not set.

CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
#
# Default contiguous memory area size:
#
CONFIG_CMA_SIZE_MBYTES=192
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8
CONFIG_CMA_AREAS=7

(taken from https://forum.kodi.tv/showthread.php?tid=254202)

@zador-blood-stained

This comment has been minimized.

Show comment
Hide comment
@zador-blood-stained

zador-blood-stained Sep 6, 2017

Member

Default CMA size is set to 16M, can be changed by using the cma kernel parameter, i.e. on recent enough images - by adding

extraargs=cma=192M

to /boot/armbianEnv.txt

Member

zador-blood-stained commented Sep 6, 2017

Default CMA size is set to 16M, can be changed by using the cma kernel parameter, i.e. on recent enough images - by adding

extraargs=cma=192M

to /boot/armbianEnv.txt

@iavael

This comment has been minimized.

Show comment
Hide comment
@iavael

iavael commented Sep 7, 2017

thanks

@PiPoly

This comment has been minimized.

Show comment
Hide comment
@PiPoly

PiPoly Oct 13, 2017

Sorry to dig up this subject but with my cubietruck I have an issue with the CMA.
With the last build, debian server version, legacy kernel, the board start and works very well with cma at default value (16M) but if I change cma kernel parameter by adding extraargs=cma=192M to /boot/armbianEnv.txt and I reboot. Then my board doesn't start, it's just display the bootloader initialisation and it's reboot.

PiPoly commented Oct 13, 2017

Sorry to dig up this subject but with my cubietruck I have an issue with the CMA.
With the last build, debian server version, legacy kernel, the board start and works very well with cma at default value (16M) but if I change cma kernel parameter by adding extraargs=cma=192M to /boot/armbianEnv.txt and I reboot. Then my board doesn't start, it's just display the bootloader initialisation and it's reboot.

@iavael

This comment has been minimized.

Show comment
Hide comment
@iavael

iavael Oct 15, 2017

@PiPoly cma=96M is enough to activate GLES and VDPAU.

iavael commented Oct 15, 2017

@PiPoly cma=96M is enough to activate GLES and VDPAU.

@PiPoly

This comment has been minimized.

Show comment
Hide comment
@PiPoly

PiPoly Oct 15, 2017

ok big thanks @iavael it's working with the configuration extraargs=cma=96M
But I don't understand why it's doesn't work with 128M or 192M. If somewone can explain me.
Ps: I work with a cubietruck.

PiPoly commented Oct 15, 2017

ok big thanks @iavael it's working with the configuration extraargs=cma=96M
But I don't understand why it's doesn't work with 128M or 192M. If somewone can explain me.
Ps: I work with a cubietruck.

@iavael

This comment has been minimized.

Show comment
Hide comment
@iavael

iavael Oct 15, 2017

There's a hardcoded limit for CMA size.

This string in dmesg gives a hint

UMP<2>: Using CMA memory backend, allocation limit: 134217728

iavael commented Oct 15, 2017

There's a hardcoded limit for CMA size.

This string in dmesg gives a hint

UMP<2>: Using CMA memory backend, allocation limit: 134217728
@PiPoly

This comment has been minimized.

Show comment
Hide comment
@PiPoly

PiPoly Mar 20, 2018

Hello, I can't change CMA more than 100M after that my board doesn't start and reboot in loop.
I need to increase the cma to 128M at least.
It was working with the version Armbian_5.11_Cubietruck_Ubuntu_trusty_3.4.112
Where is the difference between this version and now?
Thanks

PiPoly commented Mar 20, 2018

Hello, I can't change CMA more than 100M after that my board doesn't start and reboot in loop.
I need to increase the cma to 128M at least.
It was working with the version Armbian_5.11_Cubietruck_Ubuntu_trusty_3.4.112
Where is the difference between this version and now?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment