Re: [yocto] [Query] Process of Up-streaming a new meta layer

[Paul Eggleton]

On Mon, 04 Apr 2016 14:44:35 Alexander Kanavin wrote:
> On 04/03/2016 05:02 AM, Jaggi, Manish wrote:
> >> You need to publish the layer somewhere public (e.g. github), and then
> > 
> > how to publish the layer to git.yoctoproject.org instead of github ?
> 
> Do you have a reason to have your layer on git.yoctoproject.org instead
> of any other repo service? There is no automatic access control
> management there, and no pull requests support, and no issues database,
> and no wiki, so I think it's inferior and more awkward.

Nevertheless, git.yoctoproject.org is available for anyone who would like to 
host Yocto Project / OpenEmbedded related repositories. If you'd like a 
repository there please feel free to email mich...@yoctoproject.org with your 
request (and your SSH public key attached).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc

[Andrei Gherzan]

Hello,

On Mon, Apr 04, 2016 at 09:45:55PM +0200, Herrie wrote:
>
> Andrei,
>
> Hopefully better like this. Changed it to plain text at my end now for below
> patch
>

Sadly nothing changed. Lines are still wrapped breaking the patch.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Mar. 8, 2016 8:00 AM US Pacific Time

[Jolley, Stephen K]

Tuesday, April 5, 2016 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features

* Opens - 10 min

* Team Sharing - 10 min





We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/monthly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Append to bblayers.conf and local.conf

[Paul Eggleton]

On Mon, 04 Apr 2016 14:57:06 Nicolas Dechesne wrote:
> On Mon, Apr 4, 2016 at 2:43 PM, Olsson Rikard (RBSN/ESW1)
> 
>  wrote:
> > Thanks for your answer. Will these two files conf/auto.conf and
> > conf/site.conf be able to handle changes for bblayers.conf as well?
>
> no.
> 
> > For example we need to add meta-qt5 but would prefer to append to the
> > layers already there and not add our changes into bblayers.conf to avoid
> > merge work.
>
> bblayers.conf is parsed by bitbake directly, and i don't think you can
> use another file for it. Khem's suggestion to use "bitbake-layer
> add-layer" would let you override bblayers.conf 'dynamically' without
> having to archive it..

In case it's not clear, all bitbake-layers add-layer does is provide you with 
an easy way to modify bblayers.conf.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc

[Herrie]

Andrei,

Hopefully better like this. Changed it to plain text at my end now for 
below patch


Cheers,
Herman


From 164d6ec1b054fa241e65ac4961d204edd9965061 Mon Sep 17 00:00:00 2001
From: Alan Stice 
Date: Thu, 10 Mar 2016 08:52:07 -0800
Subject: [PATCH] linux-raspberrypi: Rename linux.inc to linux-rpi.inc
Rename linux.inc to prevent it from impacting other machines while 
building multiple targets with same architecture sharing sstate.


Signed-off-by: Alan Stice 
Signed-off-by: Herman van Hazendonk 
---
 recipes-kernel/linux/linux-raspberrypi.inc |   2 +-
 recipes-kernel/linux/linux-rpi.inc | 132 
+
 recipes-kernel/linux/linux.inc | 132 
-

 3 files changed, 133 insertions(+), 133 deletions(-)
 create mode 100644 recipes-kernel/linux/linux-rpi.inc
 delete mode 100644 recipes-kernel/linux/linux.inc

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc

index 24e7fe2..7ab1de2 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -1,4 +1,4 @@
-require linux.inc
+require linux-rpi.inc
 inherit linux-raspberrypi-base

 DESCRIPTION = "Linux Kernel for Raspberry Pi"
diff --git a/recipes-kernel/linux/linux-rpi.inc 
b/recipes-kernel/linux/linux-rpi.inc

new file mode 100644
index 000..fae78b7
--- /dev/null
+++ b/recipes-kernel/linux/linux-rpi.inc
@@ -0,0 +1,132 @@
+DESCRIPTION = "Linux Kernel"
+SECTION = "kernel"
+LICENSE = "GPLv2"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
+
+inherit kernel siteinfo
+require recipes-kernel/linux/linux-yocto.inc
+
+# Enable OABI compat for people stuck with obsolete userspace
+ARM_KEEP_OABI ?= "1"
+
+# Quirk for udev greater or equal 141
+UDEV_GE_141 ?= "1"
+
+# Set the verbosity of kernel messages during runtime
+# You can define CMDLINE_DEBUG in your local.conf or distro.conf to 
override this behaviour
+CMDLINE_DEBUG ?= '${@base_conditional("DISTRO_TYPE", "release", 
"quiet", "debug", d)}'

+CMDLINE_append = " ${CMDLINE_DEBUG}"
+
+# Set a variable in .configure
+# $1 - Configure variable to be set
+# $2 - value [n/y/value]
+kernel_configure_variable() {
+# Remove the config
+CONF_SED_SCRIPT="$CONF_SED_SCRIPT /CONFIG_$1[ =]/d;"
+if test "$2" = "n"
+then
+echo "# CONFIG_$1 is not set" >> ${B}/.config
+else
+echo "CONFIG_$1=$2" >> ${B}/.config
+fi
+}
+
+do_configure_prepend() {
+# Clean .config
+echo "" > ${B}/.config
+CONF_SED_SCRIPT=""
+
+# oabi / eabi support
+if [ "${TARGET_OS}" = "linux-gnueabi" -o  "${TARGET_OS}" = 
"linux-uclibceabi" ]; then

+kernel_configure_variable AEABI y
+if [ "${ARM_KEEP_OABI}" = "1" ] ; then
+kernel_configure_variable OABI_COMPAT y
+else
+kernel_configure_variable OABI_COMPAT n
+fi
+else
+kernel_configure_variable AEABI n
+kernel_configure_variable OABI_COMPAT n
+fi
+
+# Set cmdline
+kernel_configure_variable CMDLINE "\"${CMDLINE}\""
+
+# Localversion
+kernel_configure_variable LOCALVERSION "\"\""
+kernel_configure_variable LOCALVERSION_AUTO n
+
+# Udev quirks
+# Newer versions of udev mandate that sysfs doesn't have deprecated 
entries

+if [ "${UDEV_GE_141}" = "1" ] ; then
+kernel_configure_variable SYSFS_DEPRECATED n
+kernel_configure_variable SYSFS_DEPRECATED_V2 n
+kernel_configure_variable HOTPLUG y
+kernel_configure_variable UEVENT_HELPER_PATH "\"\""
+kernel_configure_variable UNIX y
+kernel_configure_variable SYSFS y
+kernel_configure_variable PROC_FS y
+kernel_configure_variable TMPFS y
+kernel_configure_variable INOTIFY_USER y
+kernel_configure_variable SIGNALFD y
+kernel_configure_variable TMPFS_POSIX_ACL y
+kernel_configure_variable BLK_DEV_BSG y
+kernel_configure_variable DEVTMPFS y
+kernel_configure_variable DEVTMPFS_MOUNT y
+fi
+
+# Newer inits like systemd need cgroup support
+if [ "${KERNEL_ENABLE_CGROUPS}" = "1" ] ; then
+kernel_configure_variable CGROUP_SCHED y
+kernel_configure_variable CGROUPS y
+kernel_configure_variable CGROUP_NS y
+kernel_configure_variable CGROUP_FREEZER y
+kernel_configure_variable CGROUP_DEVICE y
+kernel_configure_variable CPUSETS y
+kernel_configure_variable PROC_PID_CPUSET y
+kernel_configure_variable CGROUP_CPUACCT y
+kernel_configure_variable RESOURCE_COUNTERS y
+fi
+
+# root-over-nfs-over-usb-eth support. Limited, but should cover 
some cases

+# Enable this by setting a proper CMDLINE_NFSROOT_USB.
+if [ ! -z "${CMDLINE_NFSROOT_USB}" ]; then
+oenote "Configuring the kernel for root-over-nfs-over-usb-eth 
with CMDLINE ${CMDLINE_NFSROOT_USB}"

+kernel_configure_variable INET y
+kernel_con

[yocto] [meta-raspberrypi][PATCH v2 1/1] README: Mention all the supported machines

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 README | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 536926b..cfd83b3 100644
--- a/README
+++ b/README
@@ -73,7 +73,11 @@ revision: HEAD
 a. source poky/oe-init-build-env rpi-build
 b. Add needed layer to bblayers.conf:
 - meta-raspberrypi
-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
+c. Set MACHINE in local.conf to one of the supported boards:
+- raspberrypi
+- raspberrypi0
+- raspberrypi2
+- raspberrypi3
 d. bitbake rpi-hwup-image
 e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
 f. Boot your RPI.
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc

[Andrei Gherzan]

Hello,

On Mon, Apr 04, 2016 at 08:40:32PM +0200, Herrie wrote:
> From 164d6ec1b054fa241e65ac4961d204edd9965061 Mon Sep 17 00:00:00 2001
> From: Alan Stice 
> Date: Thu, 10 Mar 2016 08:52:07 -0800
> Subject: [PATCH] linux-raspberrypi: Rename linux.inc to linux-rpi.inc Rename
>  linux.inc to prevent it from impacting other machines while building
> multiple targets with same architecture sharing sstate.
>
> Signed-off-by: Alan Stice 
> Signed-off-by: Herman van Hazendonk 
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc |   2 +-
>  recipes-kernel/linux/linux-rpi.inc | 132
> +
>  recipes-kernel/linux/linux.inc | 132
> -
>  3 files changed, 133 insertions(+), 133 deletions(-)
>  create mode 100644 recipes-kernel/linux/linux-rpi.inc
>  delete mode 100644 recipes-kernel/linux/linux.inc
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 24e7fe2..7ab1de2 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -1,4 +1,4 @@
> -require linux.inc
> +require linux-rpi.inc
>  inherit linux-raspberrypi-base
>
>  DESCRIPTION = "Linux Kernel for Raspberry Pi"
> diff --git a/recipes-kernel/linux/linux-rpi.inc
> b/recipes-kernel/linux/linux-rpi.inc
> new file mode 100644
> index 000..fae78b7
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-rpi.inc
> @@ -0,0 +1,132 @@
> +DESCRIPTION = "Linux Kernel"
> +SECTION = "kernel"
> +LICENSE = "GPLv2"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> +
> +inherit kernel siteinfo
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +# Enable OABI compat for people stuck with obsolete userspace
> +ARM_KEEP_OABI ?= "1"
> +
> +# Quirk for udev greater or equal 141
> +UDEV_GE_141 ?= "1"
> +
> +# Set the verbosity of kernel messages during runtime
> +# You can define CMDLINE_DEBUG in your local.conf or distro.conf to
> override this behaviour
> +CMDLINE_DEBUG ?= '${@base_conditional("DISTRO_TYPE", "release", "quiet",
> "debug", d)}'

There seems to be issues in applying this patch as some of the lines get
wrapped to (probably) 80 chars or so. Could you please make sure you
send this patch in plain text and without this wrapping? Thanks man.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc

[Herrie]

From 164d6ec1b054fa241e65ac4961d204edd9965061 Mon Sep 17 00:00:00 2001
From: Alan Stice 
Date: Thu, 10 Mar 2016 08:52:07 -0800
Subject: [PATCH] linux-raspberrypi: Rename linux.inc to linux-rpi.inc Rename
 linux.inc to prevent it from impacting other machines while building 
multiple targets with same architecture sharing sstate.


Signed-off-by: Alan Stice 
Signed-off-by: Herman van Hazendonk 
---
 recipes-kernel/linux/linux-raspberrypi.inc |   2 +-
 recipes-kernel/linux/linux-rpi.inc | 132 
+
 recipes-kernel/linux/linux.inc | 132 
-

 3 files changed, 133 insertions(+), 133 deletions(-)
 create mode 100644 recipes-kernel/linux/linux-rpi.inc
 delete mode 100644 recipes-kernel/linux/linux.inc

diff --git a/recipes-kernel/linux/linux-raspberrypi.inc 
b/recipes-kernel/linux/linux-raspberrypi.inc

index 24e7fe2..7ab1de2 100644
--- a/recipes-kernel/linux/linux-raspberrypi.inc
+++ b/recipes-kernel/linux/linux-raspberrypi.inc
@@ -1,4 +1,4 @@
-require linux.inc
+require linux-rpi.inc
 inherit linux-raspberrypi-base

 DESCRIPTION = "Linux Kernel for Raspberry Pi"
diff --git a/recipes-kernel/linux/linux-rpi.inc 
b/recipes-kernel/linux/linux-rpi.inc

new file mode 100644
index 000..fae78b7
--- /dev/null
+++ b/recipes-kernel/linux/linux-rpi.inc
@@ -0,0 +1,132 @@
+DESCRIPTION = "Linux Kernel"
+SECTION = "kernel"
+LICENSE = "GPLv2"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
+
+inherit kernel siteinfo
+require recipes-kernel/linux/linux-yocto.inc
+
+# Enable OABI compat for people stuck with obsolete userspace
+ARM_KEEP_OABI ?= "1"
+
+# Quirk for udev greater or equal 141
+UDEV_GE_141 ?= "1"
+
+# Set the verbosity of kernel messages during runtime
+# You can define CMDLINE_DEBUG in your local.conf or distro.conf to 
override this behaviour
+CMDLINE_DEBUG ?= '${@base_conditional("DISTRO_TYPE", "release", 
"quiet", "debug", d)}'

+CMDLINE_append = " ${CMDLINE_DEBUG}"
+
+# Set a variable in .configure
+# $1 - Configure variable to be set
+# $2 - value [n/y/value]
+kernel_configure_variable() {
+# Remove the config
+CONF_SED_SCRIPT="$CONF_SED_SCRIPT /CONFIG_$1[ =]/d;"
+if test "$2" = "n"
+then
+echo "# CONFIG_$1 is not set" >> ${B}/.config
+else
+echo "CONFIG_$1=$2" >> ${B}/.config
+fi
+}
+
+do_configure_prepend() {
+# Clean .config
+echo "" > ${B}/.config
+CONF_SED_SCRIPT=""
+
+# oabi / eabi support
+if [ "${TARGET_OS}" = "linux-gnueabi" -o  "${TARGET_OS}" = 
"linux-uclibceabi" ]; then

+kernel_configure_variable AEABI y
+if [ "${ARM_KEEP_OABI}" = "1" ] ; then
+kernel_configure_variable OABI_COMPAT y
+else
+kernel_configure_variable OABI_COMPAT n
+fi
+else
+kernel_configure_variable AEABI n
+kernel_configure_variable OABI_COMPAT n
+fi
+
+# Set cmdline
+kernel_configure_variable CMDLINE "\"${CMDLINE}\""
+
+# Localversion
+kernel_configure_variable LOCALVERSION "\"\""
+kernel_configure_variable LOCALVERSION_AUTO n
+
+# Udev quirks
+# Newer versions of udev mandate that sysfs doesn't have deprecated 
entries

+if [ "${UDEV_GE_141}" = "1" ] ; then
+kernel_configure_variable SYSFS_DEPRECATED n
+kernel_configure_variable SYSFS_DEPRECATED_V2 n
+kernel_configure_variable HOTPLUG y
+kernel_configure_variable UEVENT_HELPER_PATH "\"\""
+kernel_configure_variable UNIX y
+kernel_configure_variable SYSFS y
+kernel_configure_variable PROC_FS y
+kernel_configure_variable TMPFS y
+kernel_configure_variable INOTIFY_USER y
+kernel_configure_variable SIGNALFD y
+kernel_configure_variable TMPFS_POSIX_ACL y
+kernel_configure_variable BLK_DEV_BSG y
+kernel_configure_variable DEVTMPFS y
+kernel_configure_variable DEVTMPFS_MOUNT y
+fi
+
+# Newer inits like systemd need cgroup support
+if [ "${KERNEL_ENABLE_CGROUPS}" = "1" ] ; then
+kernel_configure_variable CGROUP_SCHED y
+kernel_configure_variable CGROUPS y
+kernel_configure_variable CGROUP_NS y
+kernel_configure_variable CGROUP_FREEZER y
+kernel_configure_variable CGROUP_DEVICE y
+kernel_configure_variable CPUSETS y
+kernel_configure_variable PROC_PID_CPUSET y
+kernel_configure_variable CGROUP_CPUACCT y
+kernel_configure_variable RESOURCE_COUNTERS y
+fi
+
+# root-over-nfs-over-usb-eth support. Limited, but should cover 
some cases

+# Enable this by setting a proper CMDLINE_NFSROOT_USB.
+if [ ! -z "${CMDLINE_NFSROOT_USB}" ]; then
+oenote "Configuring the kernel for root-over-nfs-over-usb-eth 
with CMDLINE ${CMDLINE_NFSROOT_USB}"

+kernel_configure_variable INET y
+kernel_configure_variable IP_PNP y
+kernel_configure_variable USB_GADGET y
+kernel_configure_variable USB_

Re: [yocto] [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines

[Andrei Gherzan]

On Mon, Apr 04, 2016 at 08:33:00PM +0200, Petter Mabäcker wrote:
> On 04/04/2016 07:54 PM, Andrei Gherzan wrote:
> >Signed-off-by: Andrei Gherzan 
> >---
> >  README | 5 -
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> >diff --git a/README b/README
> >index 536926b..542b135 100644
> >--- a/README
> >+++ b/README
> >@@ -73,7 +73,10 @@ revision: HEAD
> >  a. source poky/oe-init-build-env rpi-build
> >  b. Add needed layer to bblayers.conf:
> >  - meta-raspberrypi
> >-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
> >+c. Set MACHINE in local.conf to one of the supported boards:
> >+- raspberrypi
> >+- raspberrypi2
> >+- raspberrypi3
> >  d. bitbake rpi-hwup-image
> >  e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is 
> > used)
> >  f. Boot your RPI.
> Good, this is a tiny but important change! Should we also mention
> raspberrypi0? Currently it just includes raspberrypi.conf and the the
> raspberrypi0 MACHINEOVERRIDE isn't used for anything, but still it is a
> defined MACHINE. What do you think?
>

Forgot it. Will send PR2.

> BR Petter

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines

[Petter Mabäcker]

On 04/04/2016 07:54 PM, Andrei Gherzan wrote:

Signed-off-by: Andrei Gherzan 
---
  README | 5 -
  1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 536926b..542b135 100644
--- a/README
+++ b/README
@@ -73,7 +73,10 @@ revision: HEAD
  a. source poky/oe-init-build-env rpi-build
  b. Add needed layer to bblayers.conf:
  - meta-raspberrypi
-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
+c. Set MACHINE in local.conf to one of the supported boards:
+- raspberrypi
+- raspberrypi2
+- raspberrypi3
  d. bitbake rpi-hwup-image
  e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is 
used)
  f. Boot your RPI.
Good, this is a tiny but important change! Should we also mention 
raspberrypi0? Currently it just includes raspberrypi.conf and the the 
raspberrypi0 MACHINEOVERRIDE isn't used for anything, but still it is a 
defined MACHINE. What do you think?


BR Petter
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH 1/1] README: Mention all the supported machines

[Andrei Gherzan]

Signed-off-by: Andrei Gherzan 
---
 README | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/README b/README
index 536926b..542b135 100644
--- a/README
+++ b/README
@@ -73,7 +73,10 @@ revision: HEAD
 a. source poky/oe-init-build-env rpi-build
 b. Add needed layer to bblayers.conf:
 - meta-raspberrypi
-c. Set MACHINE to "raspberrypi"/"raspberrypi2" in local.conf
+c. Set MACHINE in local.conf to one of the supported boards:
+- raspberrypi
+- raspberrypi2
+- raspberrypi3
 d. bitbake rpi-hwup-image
 e. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
 f. Boot your RPI.
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-selinux][PATCH 0/3] refpolicy virtual package

[Joe MacDonald]

[[yocto] [meta-selinux][PATCH 0/3] refpolicy virtual package] On 16.04.04 (Mon 
00:21) Philip Tricca wrote:

> We currently require each image to depend on the policy (or multiple
> policies) that they want installed and the selinux-config package
> enables the DEFAULT_POLICY. Since only one policy can be in effect at a
> time, and we're targeting "embedded" systems it makes sense (to me at
> least) that we would treat the policy much like we do the kernel and use
> a virtual provider.
> 
> Feedback would be much appreciated,
> Philip
> 
> Philip Tricca (3):
>   refpolicy: Setup virtual/refpolicy provider.
>   Integrate selinux-config into refpolicy_common.
>   refpolicy_common: Sanity test DEFAULT_ENFORCING value and set default.
> 
>  conf/distro/oe-selinux.conf|  1 +
>  .../packagegroups/packagegroup-core-selinux.bb |  4 +-
>  .../packagegroups/packagegroup-selinux-minimal.bb  |  3 +-
>  recipes-security/refpolicy/refpolicy_common.inc| 43 
> +-
>  recipes-security/selinux/selinux-config_0.1.bb | 41 -
>  5 files changed, 44 insertions(+), 48 deletions(-)
>  delete mode 100644 recipes-security/selinux/selinux-config_0.1.bb

I've tried this out today and it all looks good to me, I've tried
breaking the sanity check on DEFAULT_ENFORCING as we discussed and it
still seems to do the right thing.  Since this is what we were
discussing last week and it seemed to make sense at the time, I went
ahead and merged your patches for you.

-- 
-Joe MacDonald.
:wq


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Adding more screens / PiTFT support.

[Andrei Gherzan]

On Mon, Apr 04, 2016 at 05:09:03PM +0200, Petter Mabäcker wrote:
>
>
> 2016-04-04 15:17 skrev GUEYTAT Julien:
>
> > Hi,
> >
> > I would like to
> add PiTFT support to the meta-raspberry layer. Or at least I would like
> to add it in my own BSP layer.
> >
> > I read that Peter were playing with
> that recently. Could you please give me some hints to do so?
> >
> > I
> have at least two more screens to integrate.
> >
> > If someone could
> point me to an example of a BSP based on meta-raspberrypi that would be
> awesome.
> >
> > Thanks in advance,
> >
> > Best Regards
> >
> > JULIEN
> GUEYTAT
> >
> > INGÉNIEUR INFORMATIQUE
> >
> > 1027, avenue du Docteur
> Julien Lefebre BP27
> >
> > 06271 Villeneuve-Loubet Cedex
> >
> > Fixe : +33
> (0) 492 024 545
> > Mob : +33(0) 617 980 383
> > Fax : +33(0) 492 024 546
> >
> Email : j.guey...@cdssoft.studiel.fr
> >
> > www : www.studiel.fr [1]
> >
>
> > PPENSEZ ENVIRONNEMENT, IMPRIMEZ SEULEMENT SI NÉCESSAIRE
>
> Hi Julien,
>
>
> After some discussions with the community, we decided that the
> official meta-raspberrypi pitft support should be added using
> MACHINE_FEATURES. If you look in README for meta-raspberrypi there are
> some basic description about how to enable support:
>
> For a already
> supported pitft model (pitft22 is supported and 28r is on it's way
> https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html),
> you can just add below MACHINE_FEATURES to local.conf:
>
>
> MACHINE_FEATURES += "pitft pitft22"
>
> In order to add support for
> additional models you can use
> https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html as
> a reference.
>  Basically what you need are to:
>
> * add the overlay for
> the screen
>
> * Add dtoverlay option with wanted default arguments in
> rpi-config_git.bb
>
> * Add a default calibration (if needed)
>
> Assuming
> an overlay exists for your model, it shouldn't be so tricky to fix the
> rest..
>

As Petter says, everything should be in the README. Try to give it a
spin and tell us how it goes.

--
Andrei Gherzan


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Query] Process of Up-streaming a new meta layer

[Jaggi, Manish]

___
>From: yocto-boun...@yoctoproject.org  on 
>behalf of Alexander Kanavin 
>Sent: Thursday, March 31, 2016 3:48 PM
>To: yocto@yoctoproject.org
>Subject: Re: [yocto] [Query] Process of Up-streaming a new meta layer

>>On 03/23/2016 04:24 PM, Jaggi, Manish wrote:

>> What is the process of upstreaming a new meta layer ?
>> The layer is specific to cavium thunderx and it can be named as meta-cavium
>>
>> Is this the correct mailing list to upstream ?
>
>You need to publish the layer somewhere public (e.g. github), and then

how to publish the layer to git.yoctoproject.org instead of github ?

>fill out the form at http://layers.openembedded.org so it's added to the
>layer index.
>
>Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

[Trevor Woerner]

On Mon 2016-04-04 @ 08:06:30 AM, Trevor Woerner wrote:
> On Mon 2016-04-04 @ 04:32:41 PM, Gary Thomas wrote:
> > On 04/04/2016 03:24 PM, Trevor Woerner wrote:
> > >The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
> > >/dev/ttyAMA0.
> > >
> > >Signed-off-by: Trevor Woerner 
> > >---
> > >  conf/machine/raspberrypi3.conf | 2 ++
> > >  1 file changed, 2 insertions(+)
> > >
> > >diff --git a/conf/machine/raspberrypi3.conf 
> > >b/conf/machine/raspberrypi3.conf
> > >index 1b73f2f..2c3df41 100644
> > >--- a/conf/machine/raspberrypi3.conf
> > >+++ b/conf/machine/raspberrypi3.conf
> > >@@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
> > >  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
> > >
> > >  include conf/machine/raspberrypi2.conf
> > >+
> > >+SERIAL_CONSOLE_raspberrypi3 = "115200 ttyS0"
> > >
> > 
> > Why the _raspberrypi3 modifier?  Wouldn't SERIAL_CONSOLE = "115200 ttyS0" 
> > do?
> 
> oh, I see what you mean. maybe, let me check

yep, that works too ;-)

v2 to follow

> 
> > 
> > -- 
> > 
> > Gary Thomas |  Consulting for the
> > MLB Associates  |Embedded world
> > 
> > -- 
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] Adding more screens / PiTFT support.

[Petter Mabäcker]

 

2016-04-04 15:17 skrev GUEYTAT Julien: 

> Hi, 
> 
> I would like to
add PiTFT support to the meta-raspberry layer. Or at least I would like
to add it in my own BSP layer. 
> 
> I read that Peter were playing with
that recently. Could you please give me some hints to do so? 
> 
> I
have at least two more screens to integrate. 
> 
> If someone could
point me to an example of a BSP based on meta-raspberrypi that would be
awesome. 
> 
> Thanks in advance, 
> 
> Best Regards 
> 
> JULIEN
GUEYTAT 
> 
> INGÉNIEUR INFORMATIQUE 
> 
> 1027, avenue du Docteur
Julien Lefebre BP27 
> 
> 06271 Villeneuve-Loubet Cedex 
> 
> Fixe : +33
(0) 492 024 545
> Mob : +33(0) 617 980 383
> Fax : +33(0) 492 024 546
>
Email : j.guey...@cdssoft.studiel.fr 
> 
> www : www.studiel.fr [1] 
>

> PPENSEZ ENVIRONNEMENT, IMPRIMEZ SEULEMENT SI NÉCESSAIRE

Hi Julien,


After some discussions with the community, we decided that the
official meta-raspberrypi pitft support should be added using
MACHINE_FEATURES. If you look in README for meta-raspberrypi there are
some basic description about how to enable support: 

For a already
supported pitft model (pitft22 is supported and 28r is on it's way
https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html),
you can just add below MACHINE_FEATURES to local.conf:


MACHINE_FEATURES += "pitft pitft22" 

In order to add support for
additional models you can use
https://lists.yoctoproject.org/pipermail/yocto/2016-March/029284.html as
a reference.
 Basically what you need are to: 

* add the overlay for
the screen 

* Add dtoverlay option with wanted default arguments in
rpi-config_git.bb 

* Add a default calibration (if needed) 

Assuming
an overlay exists for your model, it shouldn't be so tricky to fix the
rest.. 

BR Petter 

Petter Mabäcker

Technux

www.technux.se
 

Links:
--
[1]
http://www.studiel.fr/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberry] Raspberry Pi 3

[Trevor Woerner]

On Sun 2016-04-03 @ 07:29:59 PM, Khem Raj wrote:
> On Sun, Apr 3, 2016 at 6:38 PM, Trevor Woerner  wrote:
> > Thanks to everyone for their help!! It looks like I've got something 
> > working,
> > not sure if this is a "solution" or if most would just consider it a
> > work-around:
> >
> > 1) use Andrei's meta-raspberrypi layer (which selects linux kernel 4.1 by
> > default)
> 
> thats good.

Here's some more details that will, hopefully, help others duplicate my
results:

Build Configuration:
BB_VERSION= "1.29.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "openSUSE-project-13.2"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "raspberrypi3"
DISTRO= "poky"
DISTRO_VERSION= "2.0+snapshot-20160404"
TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 
callconvention-hard cortexa7"
TARGET_FPU= "hard"
meta-raspberrypi  = 
"contrib/twoerner/raspi3:7037617fca920f6e26c2a6968fa1ec67f495035d"
meta-poky
meta  = "master:af5f423887d1c41cf7279f6e537077726ae13082"

meta-raspberrypi
git://git.yoctoproject.org/meta-raspberrypi
(branch based on master at 
84af6e7de3b8ea64ab374028aa95dc3a288ae85c)

meta-poky
git://git.yoctoproject.org/poky

My bblayers just pulls in these two layers, my local.conf has no local tweaks,
and you need to apply the two patches I recently sent to the mailing list.



> 
> >
> > 2) add the following to your local.conf:
> >
> > SERIAL_CONSOLE_forcevariable = "115200 ttyS0"
> > CORE_FREQ = "250"
> 
> Send a patch to document this in README.
> 
> >
> > 3) ??
> >
> > 4) profit!!
> >
> > I've tested with poky building both core-image-x11 and
> > core-image-full-cmdline.
> >
> > Best regards,
> > Trevor
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

[Trevor Woerner]

On Mon 2016-04-04 @ 04:32:41 PM, Gary Thomas wrote:
> On 04/04/2016 03:24 PM, Trevor Woerner wrote:
> >The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
> >/dev/ttyAMA0.
> >
> >Signed-off-by: Trevor Woerner 
> >---
> >  conf/machine/raspberrypi3.conf | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> >diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> >index 1b73f2f..2c3df41 100644
> >--- a/conf/machine/raspberrypi3.conf
> >+++ b/conf/machine/raspberrypi3.conf
> >@@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
> >  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
> >
> >  include conf/machine/raspberrypi2.conf
> >+
> >+SERIAL_CONSOLE_raspberrypi3 = "115200 ttyS0"
> >
> 
> Why the _raspberrypi3 modifier?  Wouldn't SERIAL_CONSOLE = "115200 ttyS0" do?

oh, I see what you mean. maybe, let me check

> 
> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

[Trevor Woerner]

On Mon 2016-04-04 @ 04:32:41 PM, Gary Thomas wrote:
> On 04/04/2016 03:24 PM, Trevor Woerner wrote:
> >The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
> >/dev/ttyAMA0.
> >
> >Signed-off-by: Trevor Woerner 
> >---
> >  conf/machine/raspberrypi3.conf | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> >diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
> >index 1b73f2f..2c3df41 100644
> >--- a/conf/machine/raspberrypi3.conf
> >+++ b/conf/machine/raspberrypi3.conf
> >@@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
> >  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
> >
> >  include conf/machine/raspberrypi2.conf
> >+
> >+SERIAL_CONSOLE_raspberrypi3 = "115200 ttyS0"
> >
> 
> Why the _raspberrypi3 modifier?  Wouldn't SERIAL_CONSOLE = "115200 ttyS0" do?

...because the raspi3 MACHINE just basically includes/requires the raspi2
MACHINE, and the raspi2 MACHINE includes/requires include/rpi-base.inc, and
it's in rpi-base.inc that we find the SERIAL_CONSOLE definition.

Originally I had pulled out the SERIAL_CONSOLE from rpi-base and added it to
each of the raspi MACHINES, 3 of which were the same (AMA0) and one was ttyS0.
Then, looking over the patch set, I thought it would be cleaner to just keep
everything as it was and only add the ttyS0 to the raspi3 MACHINE (which
requires the override).

> 
> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

[Gary Thomas]

On 04/04/2016 03:24 PM, Trevor Woerner wrote:

The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
/dev/ttyAMA0.

Signed-off-by: Trevor Woerner 
---
  conf/machine/raspberrypi3.conf | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 1b73f2f..2c3df41 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
  MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"

  include conf/machine/raspberrypi2.conf
+
+SERIAL_CONSOLE_raspberrypi3 = "115200 ttyS0"



Why the _raspberrypi3 modifier?  Wouldn't SERIAL_CONSOLE = "115200 ttyS0" do?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][meta-raspberrypi 1/2] raspberrypi3: serial console

[Trevor Woerner]

The serial console on the Raspberry Pi 3 is located at /dev/ttyS0 and not
/dev/ttyAMA0.

Signed-off-by: Trevor Woerner 
---
 conf/machine/raspberrypi3.conf | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 1b73f2f..2c3df41 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -7,3 +7,5 @@ MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
 MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
 
 include conf/machine/raspberrypi2.conf
+
+SERIAL_CONSOLE_raspberrypi3 = "115200 ttyS0"
-- 
2.7.0.rc3

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][meta-raspberrypi 2/2] raspberrypi3: set core frequency

[Trevor Woerner]

Pegging the core frequency at 250 avoids any fluctuations of the baud rate on
the console.

See:
https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=138223

Signed-off-by: Trevor Woerner 
---
 conf/machine/raspberrypi3.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 2c3df41..9dbb192 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -9,3 +9,4 @@ MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
 include conf/machine/raspberrypi2.conf
 
 SERIAL_CONSOLE_raspberrypi3 = "115200 ttyS0"
+CORE_FREQ = "250"
-- 
2.7.0.rc3

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi] Adding more screens / PiTFT support.

[GUEYTAT Julien]

Hi,

I would like to add PiTFT support to the meta-raspberry layer. Or at least I 
would like to add it in my own BSP layer.
I read that Peter were playing with that recently. Could you please give me 
some hints to do so?
I have at least two more screens to integrate.

If someone could point me to an example of a BSP based on meta-raspberrypi that 
would be awesome.

Thanks in advance,
Best Regards

Julien GUEYTAT
Ingénieur Informatique
[Logo CDS SOFT]
1027, avenue du Docteur Julien Lefebre BP27
06271 Villeneuve-Loubet Cedex
Fixe :  +33 (0) 492 024 545
Mob :  +33(0) 617 980 383
Fax :+33(0) 492 024 546
Email : j.guey...@cdssoft.studiel.fr
www : www.studiel.fr
P Pensez Environnement, imprimez seulement si nécessaire

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Append to bblayers.conf and local.conf

[Nicolas Dechesne]

On Mon, Apr 4, 2016 at 2:43 PM, Olsson Rikard (RBSN/ESW1)
 wrote:
> Thanks for your answer. Will these two files conf/auto.conf and 
> conf/site.conf be able to handle changes for bblayers.conf as well?

no.

>
> For example we need to add meta-qt5 but would prefer to append to the layers 
> already there and not add our changes into bblayers.conf to avoid merge work.
>

bblayers.conf is parsed by bitbake directly, and i don't think you can
use another file for it. Khem's suggestion to use "bitbake-layer
add-layer" would let you override bblayers.conf 'dynamically' without
having to archive it..
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Append to bblayers.conf and local.conf

[Olsson Rikard (RBSN/ESW1)]

Hello Nicolas,

Thanks for your answer. Will these two files conf/auto.conf and conf/site.conf 
be able to handle changes for bblayers.conf as well?

For example we need to add meta-qt5 but would prefer to append to the layers 
already there and not add our changes into bblayers.conf to avoid merge work.

Best regards
Rikard Olsson




> -Original Message-
> From: Nicolas Dechesne [mailto:nicolas.deche...@linaro.org]
> Sent: den 4 april 2016 11:30
> To: Paul Eggleton 
> Cc: Olsson Rikard (RBSN/ESW1) ; Yocto list
> discussion 
> Subject: Re: [yocto] Append to bblayers.conf and local.conf
> 
> On Sun, Apr 3, 2016 at 10:54 PM, Paul Eggleton 
> wrote:
> >> We are receiving bblayer.conf and local.conf from external supplier
> >> which already have layers/configuration added. Now we want to add our
> >> own layers/configuration by appending to these files this to avoid
> >> manual merge work each time a delivery from external supplier is made.
> >>
> >> Question:
> >> How do I append layers/configuration to bblayer.conf and local.conf?
> >
> > The best answer I can give is these files aren't really meant to be
> > distributed. If you have too much specific stuff in these files
> > (particularly
> > local.conf) then I would say it's possible your supplier has put
> > things in the wrong place.
> >
> > The way it ought to work is, you add the needed layers to your
> > bblayers.conf, then go to your local.conf and set DISTRO and MACHINE
> > and anything you need for *local* configuration (e.g. local paths) and
> > that's pretty much it. If you have to include a whole bunch of extra
> > lines in local.conf, those lines really should be elsewhere (e.g.
> > custom distro config, or the machine .conf file if they are specific
> > to the machine.)
> 
> Note that you can use conf/auto.conf and conf/site.conf as well, these files 
> are
> parsed at the same time as conf/local.conf, so if you really cannot change
> local.conf, you can use the one of the other ones.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [Query] Process of Up-streaming a new meta layer

[Alexander Kanavin]

On 04/03/2016 05:02 AM, Jaggi, Manish wrote:


You need to publish the layer somewhere public (e.g. github), and then


how to publish the layer to git.yoctoproject.org instead of github ?


Do you have a reason to have your layer on git.yoctoproject.org instead 
of any other repo service? There is no automatic access control 
management there, and no pull requests support, and no issues database, 
and no wiki, so I think it's inferior and more awkward.



Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Append to bblayers.conf and local.conf

[Nicolas Dechesne]

On Sun, Apr 3, 2016 at 10:54 PM, Paul Eggleton
 wrote:
>> We are receiving bblayer.conf and local.conf from external supplier which
>> already have layers/configuration added. Now we want to add our own
>> layers/configuration by appending to these files this to avoid manual merge
>> work each time a delivery from external supplier is made.
>>
>> Question:
>> How do I append layers/configuration to bblayer.conf and local.conf?
>
> The best answer I can give is these files aren't really meant to be
> distributed. If you have too much specific stuff in these files (particularly
> local.conf) then I would say it's possible your supplier has put things in the
> wrong place.
>
> The way it ought to work is, you add the needed layers to your bblayers.conf,
> then go to your local.conf and set DISTRO and MACHINE and anything you need
> for *local* configuration (e.g. local paths) and that's pretty much it. If you
> have to include a whole bunch of extra lines in local.conf, those lines really
> should be elsewhere (e.g. custom distro config, or the machine .conf file if
> they are specific to the machine.)

Note that you can use conf/auto.conf and conf/site.conf as well, these
files are parsed at the same time as conf/local.conf, so if you really
cannot change local.conf, you can use the one of the other ones.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto