On Wed, May 18, 2016 at 11:46:39PM +0200, Andreas Müller wrote: > On Wed, May 18, 2016 at 7:32 PM, Herve Jourdain <herve.jourd...@neuf.fr> > wrote: > > One thing I didn't make configurable, but that maybe could be, is the > > parameter passed to the overlay. > > I selected cma-256, based on experience from other people, and because my > > configuration is RPI2/3 with 1G of memory. > > I realize it might not work well with RPI0/1, which have less memory > > available... > > So even if I believe cma-256 is a good default value, it might be made > > selectable by the user, if we want to consider vc4 on RPI0/1. > I played around with vc4 to but did not manage to get it work for an > elder version 4.1 of kernel. > > I did in rpi-config: > > CMA_SIZE = "cma-256" > CMA_SIZE_raspberrypi = "cma-64"
I sent reply about this too. This is definitely one solution would I
would rather have a CMA_SIZE default value and a python function to
check its match with board variant. Cause in this way a user might be
able to use cma-96 on rapsberrypi.
> CMA_SIZE_raspberrypi0 = "cma-128"
> ...
> echo "dtoverlay=vc4-kms-v3d-overlay,${CMA_SIZE}"
> >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
>
> This is nothing but an untested suggestion.
>
> Without testing your series I would be very happy to see this or very
> similar applied in master: Since vc4 works, RaspberryPi turned into my
> reference test board - e.g. have not seen kde5 running that nice on
> another board..
>
> Andreas
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Andrei Gherzan
signature.asc
Description: PGP signature
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
