[FE training-materials-updates] yocto: labs: Set to linux-ti-staging + note about providers

[Gregory Clement]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : dev_mylene/yocto_update/krogoth
Link       : http://git.free-electrons.com/training-materials/commit/?id=a2e8f1d9fdc8963602ee8aaa3f3ceb25e226be9f

>---------------------------------------------------------------

commit a2e8f1d9fdc8963602ee8aaa3f3ceb25e226be9f
Author: Mylène Josserand <mylene.josserand at free-electrons.com>
Date:   Fri Aug 19 12:18:51 2016 +0200

    yocto: labs: Set to linux-ti-staging + note about providers
    
    Set the Linux Kernel provider to "linux-ti-staging" and not "linux-yocto".
    This provider is available only in the case that meta-ti layer is
    above meta-yocto-bsp layer. See the note added in the lab for more details.
    
    Signed-off-by: Mylène Josserand <mylene.josserand at free-electrons.com>


>---------------------------------------------------------------

a2e8f1d9fdc8963602ee8aaa3f3ceb25e226be9f
 .../yocto-advanced-configuration.tex                     | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex b/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
index 5e28c36..33877c9 100644
--- a/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
+++ b/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
@@ -139,17 +139,27 @@ To see which kernel is used, dry-run BitBake:
 bitbake -vn virtual/kernel
 \end{verbatim}
 
-In our case, we can see the \code{linux-yocto} provides the
+In our case, we can see the \code{linux-ti-staging} provides the
 \code{virtual/kernel} functionality:
 \small
 \begin{verbatim}
-NOTE: selecting linux-yocto to satisfy virtual/kernel due to PREFERRED_PROVIDERS
+NOTE: selecting linux-ti-staging to satisfy virtual/kernel due to PREFERRED_PROVIDERS
 \end{verbatim}
 \normalsize
 
+% [Mylene] NOTE : With krogoth branch, the meta-yocto-bsp adds also the support
+% for the beaglebone. In this case, there is a concurency between meta-ti and
+% meta-yocto-bsp abour the PREFERRED_PROVIDERS for Linux Kernel.
+% In case the meta-ti is added after the meta-yocto-bsp in bblayers.conf, the
+% default PREFERRED_PROVIDER for the kernel will the "linux-yocto" as it will
+% take the first occurence of this variable. To have "linux-ti-staging", the
+% "meta-ti" layer must be added before "meta-yocto-bsp" in conf/bblayers.conf
+% This is currently the only solution found, we should investiguate how handle
+% it in a better way than just "order" layers !
+
 We can force Yocto to select another \code{kernel} by explicitly
 defining which one to use in our local configuration. Try switching
-from \code{linux-yocto} to \code{linux-dummy} only using the
+from \code{linux-ti-staging} to \code{linux-dummy} only using the
 local configuration.
 
 Then check the previous step worked by dry-running again BitBake.