<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-freescale.git/classes/fsl-vivante-kernel-driver-handler.bbclass, branch master</title>
<subtitle>Mirror of github.com/Freescale/meta-freescale</subtitle>
<id>https://git.enea.com/cgit/linux/meta-freescale.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-freescale.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/'/>
<updated>2022-01-25T12:55:52+00:00</updated>
<entry>
<title>fsl-vivante-kernel-driver-handler.bbclass: Fix multilib support</title>
<updated>2022-01-25T12:55:52+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2022-01-25T12:55:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=baf0596c63b816e70174c5d464e0c25196d0f7f8'/>
<id>urn:sha1:baf0596c63b816e70174c5d464e0c25196d0f7f8</id>
<content type='text'>
Building core-image-weston with multilib support and builtin graphics
fails:

```
ERROR: Nothing PROVIDES 'virtual/arm-oelmllib32-linux-gnueabi-binutils'. Close matches:
  virtual/lib32-arm-oelmllib32-linux-gnueabi-binutils
  virtual/lib32-arm-oelmllib32-linux-gnueabi-go-runtime
  virtual/lib32-arm-oelmllib32-linux-gnueabi-rust
ERROR: Nothing PROVIDES 'virtual/arm-oelmllib32-linux-gnueabi-gcc'. Close matches:
  virtual/lib32-arm-oelmllib32-linux-gnueabi-g++
  virtual/lib32-arm-oelmllib32-linux-gnueabi-gcc
  virtual/lib32-arm-oelmllib32-linux-gnueabi-rust
```

This is the configuration added in local.conf:

```
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE:virtclass-multilib-lib32 = "armv7athf-neon"
IMAGE_INSTALL:append = " lib32-glibc lib32-libgcc lib32-libstdc++"
MACHINE_USES_VIVANTE_KERNEL_DRIVER_MODULE = "0"
```

This commit fixes the provides so BitBake can properly handle the
dependencies.

Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>layer: Convert to new override syntax</title>
<updated>2021-08-12T17:08:24+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2021-08-02T18:01:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=59d36c9832702989bfcca8a5af29fb2dff01efcc'/>
<id>urn:sha1:59d36c9832702989bfcca8a5af29fb2dff01efcc</id>
<content type='text'>
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>fsl-vivante-kernel-driver-handler: Fix kernel name in variable assignment</title>
<updated>2020-02-13T02:51:44+00:00</updated>
<author>
<name>Tom Hochstein</name>
<email>tom.hochstein@nxp.com</email>
</author>
<published>2020-01-16T16:44:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=8413aafd59df1577b594e3553b767f165bb80b5e'/>
<id>urn:sha1:8413aafd59df1577b594e3553b767f165bb80b5e</id>
<content type='text'>
If the graphics driver is built into the kernel, a warning is generated
for each i.MX kernel recipe, like this:

WARNING: /home/r60874/zeus/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb: Variable key RPROVIDES_${KERNEL_PACKAGE_NAME}-base ( ${KERNEL_PACKAGE_NAME}-${KERNEL_VERSION}) replaces original key RPROVIDES_kernel-base ( kernel-module-imx-gpu-viv).

The problem is that the kernel name used in variables is no longer a
constant 'kernel', but is now parameterized:

https://github.com/openembedded/openembedded-core/commit/6c8c899849d101fd1b86aad0b8eed05c7c785924

Signed-off-by: Tom Hochstein &lt;tom.hochstein@nxp.com&gt;
</content>
</entry>
<entry>
<title>fsl-vivante-kernel-driver-handler.bbclass: Allow build for non-i.MX6</title>
<updated>2016-07-15T10:48:55+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2016-07-04T17:20:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=f7e8d04ac7e3f4564305249c43178fabd1cec30e'/>
<id>urn:sha1:f7e8d04ac7e3f4564305249c43178fabd1cec30e</id>
<content type='text'>
When building for non-i.MX6, we ought to assume the SoC does not has
Vivante GPU at all, or the build will fail. This fixes the build of
linux-fslc-imx-rt for i.MX7D as it does not have a Vivante GPU.

Change-Id: Ic8fc4808880aca381e88f6e1b6c52416bb4520c4
Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>fsl-vivante-kernel-driver-handler.bbclass: Postpone defconfig changes</title>
<updated>2016-04-19T18:03:24+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2015-12-10T16:14:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=992a522b08143886d35007f774d3a24f98c1b841'/>
<id>urn:sha1:992a522b08143886d35007f774d3a24f98c1b841</id>
<content type='text'>
The defconfig changes should be done later in the process so the
.config file is generated, using any other mean, and mangled to
respect the distribution setting regarding the module use or not.

Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>fsl-vivante-kernel-driver-handler.bbclass: Handle Vivante kernel driver provider</title>
<updated>2016-04-19T18:03:20+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2015-08-11T20:26:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=2f94562bba387c7a6ba457f66f39ac976f656f9b'/>
<id>urn:sha1:2f94562bba387c7a6ba457f66f39ac976f656f9b</id>
<content type='text'>
Enable the kernel to provide or not the Vivante kernel driver and
dynamically set the proper providers per machine.

The following options are supported:

  MACHINE_HAS_VIVANTE_KERNEL_DRIVER_SUPPORT

     Machine does or does not have support for the Vivante kernel
     driver, options are:

       0 - machine does not have Vivante GPU driver support
       1 - machine has Vivante GPU driver support

  MACHINE_USES_VIVANTE_KERNEL_DRIVER_MODULE

      Machine uses the Vivante kernel driver as module, options are:

       0 - enable the builtin kernel driver module
       1 - enable the external kernel module

Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
</feed>
