Lamobo R1 coherent_pool problem

[h0ly0ne]

Hi all,

 

I've one minor issue with my Lamobo R1. I've to set the coherent_pool to > 256KiB to get my USB DVB

device working. But every time I set the coherent_pool to e.g. 2M and regenerate the boot.scr the device

gets in an endless boot loop (starting uboot - starting kernel - changes resolution and starts to load

drivers - but then crashes with graphic errors and starts all over again).

 

Is there something I can do against this? I've compiled the v3.0 with Jessie 3.4.107 with following kernel

paramters configured (and sunxi uboot v2015.04):
 

MEDIA_SUPPORT=m
VIDEO_DEV=m
SOUND=m
GMAC_FOR_BANANAPI=y
CMA=y
CMA_SIZE_MBYTES=16
 

Greetings,

Oliver

[h0ly0ne]

Finally solved - for all other people facing the same issues:

 

Change /boot/boot.cmd from:

  setenv bootargs console=tty1 root=/dev/mmcblk0p1 rootwait .... loglevel=1

to:

  setenv bootargs "coherent_pool=6M console=tty1 root=/dev/mmcblk0p1 rootwait .... loglevel=1"

 

then make a backup of /boot/boot.scr (e.g. boot.old) and regenerate boot.scr:

mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

 

And for all other users that want to get v4l devices, not supported in kernel by default, working -

you have to recompile the image yourselves - as Igor seems not to change MEDIA_SUPPORT=Y

to MEDIA_SUPPORT=m (and VIDEO_DEV=Y to VIDEO_DEV=m) in his builds. This could be an

oversight - so take this just as a reminder - to save some people compile and troubleshooting time.

 

Greetings,

h0ly0ne

[h0ly0ne]

A few driver panics later the perfect additional module composition for kernel compilation

seems to be following configuration (at the moment running stable - more tests to come):

 

CONFIG_MEDIA_SUPPORT=m
CONFIG_VIDEO_DEV=m
CONFIG_SOUND=m
CONFIG_GMAC_FOR_BANANAPI=y
CONFIG_CMA=y
CONFIG_CMA_DEBUG=n
CONFIG_CMA_MBYTES=16
CONFIG_CMA_SIZE_SEL_MBYTES=y
CONFIG_CMA_ALIGNMENT=8
CONFIG_CMA_AREAS=7

 

Greetings,

h0ly0ne