[yocto] yocto Digest, Vol 68, Issue 81z

Denton Gentry denton.gentry at gmail.com
Sat May 21 10:22:04 PDT 2016


aXzzZdZx
On May 20, 2016 4:55 AM, <yocto-request at yoctoproject.org> wrote:

> Send yocto mailing list submissions to
>         yocto at yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
>         yocto-request at yoctoproject.org
>
> You can reach the person managing the list at
>         yocto-owner at yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
>    1. Re: [meta-raspberrypi][PATCH 5/8] Support for vc4 graphics
>       driver: upgrade 4.4 kernel to 4.4.10 (Andrei Gherzan)
>    2. Re: ***SPAM*** Re: [meta-raspberrypi][PATCH 5/8] Support for
>       vc4 graphics driver: upgrade 4.4 kernel to 4.4.10 (Herve Jourdain)
>    3. Re: ***SPAM*** Re: [meta-raspberrypi][PATCH 5/8] Support for
>       vc4 graphics driver: upgrade 4.4 kernel to 4.4.10 (Andrei Gherzan)
>    4. [meta-raspberrypi][PATCH v2 00/13] Support for VC4 graphics
>       driver (Herve Jourdain)
>    5. [meta-raspberrypi][PATCH v2 01/13] rpi-default-providers.inc:
>       change default providers to support vc4graphics (Herve Jourdain)
>    6. [meta-raspberrypi][PATCH v2 02/13] rpi-base.inc: add
>       vc4-kms-v3d to the overlays to support vc4graphics (Herve Jourdain)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 20 May 2016 12:39:35 +0200
> From: Andrei Gherzan <andrei at gherzan.ro>
> To: Khem Raj <raj.khem at gmail.com>
> Cc: Yocto Project <yocto at yoctoproject.org>
> Subject: Re: [yocto] [meta-raspberrypi][PATCH 5/8] Support for vc4
>         graphics driver: upgrade 4.4 kernel to 4.4.10
> Message-ID: <20160520103935.GI9848 at resin.home>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thu, May 19, 2016 at 09:02:04AM -0700, Khem Raj wrote:
> > On Thu, May 19, 2016 at 8:11 AM, Andrei Gherzan <andrei at gherzan.ro>
> wrote:
> > > 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.jourdain at 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"
> >
> >
> > setting CMA_SIZE should be moved into machine.conf file IMO
> >
>
> That's actually a good idea. I would say to have it in machine as a
> default value for that specific machine. And then be able to overwrite
> it as user needs. Optionally have a python function to check that what
> user requested makes sense for the selected board.
>
> --
> Andrei Gherzan
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 819 bytes
> Desc: not available
> URL: <
> http://lists.yoctoproject.org/pipermail/yocto/attachments/20160520/b258b04d/attachment-0001.pgp
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 20 May 2016 12:47:40 +0200
> From: Herve Jourdain <herve.jourdain at neuf.fr>
> To: 'Andrei Gherzan' <andrei at gherzan.ro>, 'Khem Raj'
>         <raj.khem at gmail.com>
> Cc: 'Yocto Project' <yocto at yoctoproject.org>
> Subject: Re: [yocto] ***SPAM*** Re: [meta-raspberrypi][PATCH 5/8]
>         Support for vc4 graphics driver: upgrade 4.4 kernel to 4.4.10
> Message-ID: <03f601d1b285$0a8c81f0$1fa585d0$@neuf.fr>
> Content-Type: text/plain; charset=iso-8859-1
>
> Hi Andrei, Khem,
>
> That's what I implemented in the upcoming v2 - except for the python
> checking function part.
> One thing, shall I call the variable CMA_SIZE, or VC4_CMA_SIZE?
> I know CMA is kind of common, but we're using this only to trigger a
> parameter to the v4c overlay.
> Any opinion? (in the current implementation, I went with CMA_SIZE, but I
> have doubts...)
>
> Herve
>
> -----Original Message-----
> From: yocto-bounces at yoctoproject.org [mailto:
> yocto-bounces at yoctoproject.org]
> On Behalf Of Andrei Gherzan
> Sent: vendredi 20 mai 2016 12:40
> To: Khem Raj <raj.khem at gmail.com>
> Cc: Yocto Project <yocto at yoctoproject.org>
> Subject: ***SPAM*** Re: [yocto] [meta-raspberrypi][PATCH 5/8] Support for
> vc4 graphics driver: upgrade 4.4 kernel to 4.4.10
>
> On Thu, May 19, 2016 at 09:02:04AM -0700, Khem Raj wrote:
> > On Thu, May 19, 2016 at 8:11 AM, Andrei Gherzan <andrei at gherzan.ro>
> wrote:
> > > 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.jourdain at 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"
> >
> >
> > setting CMA_SIZE should be moved into machine.conf file IMO
> >
>
> That's actually a good idea. I would say to have it in machine as a default
> value for that specific machine. And then be able to overwrite it as user
> needs. Optionally have a python function to check that what user requested
> makes sense for the selected board.
>
> --
> Andrei Gherzan
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 20 May 2016 12:51:56 +0200
> From: Andrei Gherzan <andrei at gherzan.ro>
> To: Herve Jourdain <herve.jourdain at neuf.fr>
> Cc: 'Yocto Project' <yocto at yoctoproject.org>
> Subject: Re: [yocto] ***SPAM*** Re: [meta-raspberrypi][PATCH 5/8]
>         Support for vc4 graphics driver: upgrade 4.4 kernel to 4.4.10
> Message-ID: <20160520105156.GK9848 at resin.home>
> Content-Type: text/plain; charset="us-ascii"
>
> On Fri, May 20, 2016 at 12:47:40PM +0200, Herve Jourdain wrote:
> > Hi Andrei, Khem,
> >
> > That's what I implemented in the upcoming v2 - except for the python
> > checking function part.
> > One thing, shall I call the variable CMA_SIZE, or VC4_CMA_SIZE?
> > I know CMA is kind of common, but we're using this only to trigger a
> > parameter to the v4c overlay.
> > Any opinion? (in the current implementation, I went with CMA_SIZE, but I
> > have doubts...)
> >
>
> Hint: Try to reply in line if possible. It is easier to follow the
> discussion in this way.
>
> I would vote for VC4_CMA_SIZE. It sounds safer.
>
> --
> Andrei Gherzan
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 819 bytes
> Desc: not available
> URL: <
> http://lists.yoctoproject.org/pipermail/yocto/attachments/20160520/0874bb0c/attachment-0001.pgp
> >
>
> ------------------------------
>
> Message: 4
> Date: Fri, 20 May 2016 19:51:40 +0800
> From: Herve Jourdain <herve.jourdain at neuf.fr>
> To: yocto at yoctoproject.org
> Subject: [yocto] [meta-raspberrypi][PATCH v2 00/13] Support for VC4
>         graphics driver
> Message-ID: <1463745113-55142-1-git-send-email-herve.jourdain at neuf.fr>
>
> This v2 series addresses the following issues with the first series:
> a. Fix the 4.4.10 kernel revision
> b. Effectively add vc4-kms-v3d overlay to the list of overlays to build
> (forgotten previously)
> c. Make the parameter to the v4c-kms-v3d overlay configurable
> d. Add default values for the cma parameter to the v4c-kms-v3d overlay,
> depending on the board (and the memory it has)
>
> This patch series enables the support for the VC4 graphics driver from
> Eric Anholt.
> There was a previous patch series by Javier Martinez Canillas, but it
> required use of a different kernel.
> VC4 is now supported in the raspberrypi official kernel, at least for
> 4.4.9+.
> The support in 4.1 exists, but it is NOT STABLE, so it has been deemed
> unreasonable to support VC4 with 4.1 kernels.
>
> THEREFORE, VC4 graphics is supported ONLY for kernel versions 4.4.9 and
> later.
>
> This patch series proposes to support VC4 by only adding 'vc4graphics' to
> MACHINE_FEATURES, for raspberrypi. If this is set, it will trigger all the
> necessary configuration/changes to use the VC4 driver, including
> mesa/wayland/weston currently, and adding the overlay required.
> In order for this series to work, some previous patches are needed
> (support for .dtbo, and fix of the mesa packaging when there is no DRI
> driver).
> The memory reserved for the VC4 driver has default values depending on the
> version of the board used, but it can be configured by setting VC4_CMA_SIZE
> to a value supported by the overlay ('cma-256', 'cma-192', 'cma-128',
> 'cma-96', 'cma-64').
> 'cma-256' is the recommended value, but it might not be possible on boards
> with 512MB or DRAM, or less...
> 'cma-64' is known to not being able to support FHD/1080p.
>
> It was tested with wayland/weston, without the support for X11.
>
> This patch series depends on two other patch series previously posted,
> that enable the support for .dtbo overlay files.
>
> Herve Jourdain (13):
>   rpi-default-providers.inc: change default providers to support
>     vc4graphics
>   rpi-base.inc: add vc4-kms-v3d to the overlays to support vc4graphics
>   raspberrypi.conf: set the default value of VC4_CMA_SIZE to support
>     vc4graphics
>   raspberrypi0.conf: set the default value of VC4_CMA_SIZE to support
>     vc4graphics
>   raspberrypi2.conf: set the default value of VC4_CMA_SIZE to support
>     vc4graphics
>   raspberrypi3.conf: set the default value of VC4_CMA_SIZE to support
>     vc4graphics
>   firmware.inc: bump version to support vc4graphics
>   rpi-config_git.bb: add v4c overlay to config.txt to support
>     vc4graphics
>   wayland/weston_%.bbappend: modify configuration options to support
>     vc4graphics
>   weston/weston_%.bbappend: modify configuration options to support
>     vc4graphics
>   mesa_%.bbappend: new file to add the correct configuration options to
>     support vc4graphics
>   linux-raspberrypi_4.4.bb: bump the kernel revision to 4.4.10 to
>     support vc4graphics
>   linux-rpi.inc: add the configuration options required to support
>     vc4graphics
>
>  conf/machine/include/rpi-base.inc              |  1 +
>  conf/machine/include/rpi-default-providers.inc |  8 ++++----
>  conf/machine/raspberrypi.conf                  |  2 ++
>  conf/machine/raspberrypi0.conf                 |  2 ++
>  conf/machine/raspberrypi2.conf                 |  2 ++
>  conf/machine/raspberrypi3.conf                 |  2 ++
>  recipes-bsp/bootfiles/rpi-config_git.bb        | 10 +++++++++-
>  recipes-bsp/common/firmware.inc                |  4 ++--
>  recipes-graphics/mesa/mesa_%.bbappend          |  4 ++++
>  recipes-graphics/wayland/weston_%.bbappend     |  6 ++----
>  recipes-graphics/weston/weston_%.bbappend      | 13 +++++++------
>  recipes-kernel/linux/linux-raspberrypi_4.4.bb  |  4 ++--
>  recipes-kernel/linux/linux-rpi.inc             | 10 ++++++++++
>  13 files changed, 49 insertions(+), 19 deletions(-)
>  create mode 100644 recipes-graphics/mesa/mesa_%.bbappend
>
> --
> 2.7.4
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 20 May 2016 19:51:41 +0800
> From: Herve Jourdain <herve.jourdain at neuf.fr>
> To: yocto at yoctoproject.org
> Subject: [yocto] [meta-raspberrypi][PATCH v2 01/13]
>         rpi-default-providers.inc: change default providers to support
>         vc4graphics
> Message-ID: <1463745113-55142-2-git-send-email-herve.jourdain at neuf.fr>
>
> Signed-off-by: Herve Jourdain <herve.jourdain at neuf.fr>
> ---
>  conf/machine/include/rpi-default-providers.inc | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/conf/machine/include/rpi-default-providers.inc
> b/conf/machine/include/rpi-default-providers.inc
> index cabbd43..0bc8838 100644
> --- a/conf/machine/include/rpi-default-providers.inc
> +++ b/conf/machine/include/rpi-default-providers.inc
> @@ -3,8 +3,8 @@
>  PREFERRED_PROVIDER_virtual/kernel ?= "linux-raspberrypi"
>  PREFERRED_PROVIDER_u-boot ?= "u-boot-rpi"
>  PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
> -PREFERRED_PROVIDER_virtual/egl ?= "userland"
> -PREFERRED_PROVIDER_virtual/libgles2 ?= "userland"
> -PREFERRED_PROVIDER_virtual/libgl ?= "mesa-gl"
> -PREFERRED_PROVIDER_virtual/mesa ?= "mesa-gl"
> +PREFERRED_PROVIDER_virtual/egl ?=
> "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa",
> "userland", d)}"
> +PREFERRED_PROVIDER_virtual/libgles2 ?=
> "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa",
> "userland", d)}"
> +PREFERRED_PROVIDER_virtual/libgl ?=
> "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "mesa-gl",
> d)}"
> +PREFERRED_PROVIDER_virtual/mesa ?=
> "${@bb.utils.contains("MACHINE_FEATURES", "vc4graphics", "mesa", "mesa-gl",
> d)}"
>  PREFERRED_PROVIDER_jpeg ?= "jpeg"
> --
> 2.7.4
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 20 May 2016 19:51:42 +0800
> From: Herve Jourdain <herve.jourdain at neuf.fr>
> To: yocto at yoctoproject.org
> Subject: [yocto] [meta-raspberrypi][PATCH v2 02/13] rpi-base.inc: add
>         vc4-kms-v3d to the overlays to support vc4graphics
> Message-ID: <1463745113-55142-3-git-send-email-herve.jourdain at neuf.fr>
>
> Signed-off-by: Herve Jourdain <herve.jourdain at neuf.fr>
> ---
>  conf/machine/include/rpi-base.inc | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/conf/machine/include/rpi-base.inc
> b/conf/machine/include/rpi-base.inc
> index 2c9d8e0..23f8619 100644
> --- a/conf/machine/include/rpi-base.inc
> +++ b/conf/machine/include/rpi-base.inc
> @@ -59,6 +59,7 @@ KERNEL_DEVICETREE_OVERLAYS_DTBO = " \
>      overlays/w1-gpio.dtbo \
>      overlays/w1-gpio-pullup.dtbo \
>      overlays/pi3-miniuart-bt.dtbo \
> +    overlays/vc4-kms-v3d.dtbo \
>      "
>
>  def cmpver_strings(ver1, ver2, truevalue, falsevalue):
> --
> 2.7.4
>
>
>
> ------------------------------
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> End of yocto Digest, Vol 68, Issue 81
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160521/b630691f/attachment.html>


More information about the yocto mailing list