Re: changing kernel config in Morty build

[Greg Wilson-Lindberg <GWilson@sakuraus.com>]

[-- Attachment #1.1: Type: text/plain, Size: 8828 bytes --]

Hi Bruce,
I've been able to reproduce the problem in a more minimal environment.

To build a basic Yocto Raspberry Pi environment I based my build on the instructions found here:
https://themeaningfulengineer.github.io/exploring-yocto-with-raspberrypi/

The steps that I actually executed are:

git clone -b morty --single-branch git://git.yoctoproject.org/poky
cd poky/
git clone -b morty http://git.yoctoproject.org/git/meta-raspberrypi
source oe-init-build-env rpi-build

In rpi-build/conf/local.conf I changed the MACHINE assignment to "raspberrypi2" from "qemu86"

In rpi-build/conf/bblayers.conf I added "  /home/gwilson/Qt/poky/meta-raspberrypi \" to pick up the raspberry layer.

At this point I ran:
bitbake rpi-hwup-image

to verify that the environment was correct. The build finished with only a couple of warnings about checksum problems and using alternate mirrors.


I then copied in my kernel scripts and added in the directory to the bblayers file.

When I rebuilt with these changes I get the same warnings/errors about changing the kernel config that I get with my full build environment.

I've attached my meta-test directory with the kernel configuration .bbappend and .scc & .cfg files, and the final bblayers.conf & local.conf files.

Thank you for taking a look at this.

Regards,

Greg Wilson-Lindberg





________________________________
From: yocto-bounces@yoctoproject.org <yocto-bounces@yoctoproject.org> on behalf of Greg Wilson-Lindberg <GWilson@sakuraus.com>
Sent: Friday, October 5, 2018 9:23:52 AM
To: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: [yocto] changing kernel config in Morty build

Hi Bruce,
I'll do my best to get something for you.
Thanks,

Greg Wilson-Lindberg
Principal Firmware Engineer | Sakura Finetek USA, Inc.

1750 W 214th Street | Torrance, CA 90501 | U.S.A.
T: +1 310 783 5075
F: +1 310 618 6902 | E: gwilson@sakuraus.com
www.sakuraus.com<http://www.sakuraus.com>





Confidentiality Notice: This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that Sakura Finetek USA, Inc. can arrange for proper delivery, and then please delete the message from your inbox. Thank you.



> -----Original Message-----
> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
> Sent: Friday, October 05, 2018 08:46 AM
> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>; yocto@yoctoproject.org
> Subject: Re: [yocto] changing kernel config in Morty build
>
> On 2018-10-04 4:38 PM, Greg Wilson-Lindberg wrote:
> > Does anybody else have any idea about what is going on here?
> >
>
> I can't tell from the information provided.
>
> But if you can send me a set of layers to clone, and configure locally, I can figure it
> out.
>
> Cheers,
>
> Bruce
>
> > Yocto is seeing my request to change the kernel config, suggests that
> > the change is acceptable, but then doesn't make it.
> >
> > Thanks in advance for any insight,
> >
> > Greg
> >
> > **
> >
> > *From:*Greg Wilson-Lindberg
> > *Sent:* Tuesday, October 02, 2018 02:22 PM
> > *To:* yocto@yoctoproject.org
> > *Subject:* changing kernel config in Morty build
> >
> > I'm trying to change some kernel configuration flags in a
> > raspberrypi3 Morty build and I get warnings that it isn't working.
> >
> > Here is the build info and warnings:
> >
> > Build Configuration:
> >
> > BB_VERSION        = "1.32.0"
> >
> > BUILD_SYS         = "x86_64-linux"
> >
> > NATIVELSBSTRING   = "universal"
> >
> > TARGET_SYS        = "arm-poky-linux-gnueabi"
> >
> > MACHINE           = "raspberrypi3"
> >
> > DISTRO            = "b2qt"
> >
> > DISTRO_VERSION    = "2.2.4"
> >
> > TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4
> > callconvention-hard cortexa7"
> >
> > TARGET_FPU        = "hard"
> >
> > SDKMACHINE        = "x86_64"
> >
> > meta
> >
> > meta-poky         = "HEAD:df76669bdd70aa0d903c4211dde731221c7e756d"
> >
> > meta-raspberrypi  = "HEAD:2a192261a914892019f4f428d7462bb3c585ebac"
> >
> > meta-oe
> >
> > meta-python
> >
> > meta-networking
> >
> > meta-initramfs
> >
> > meta-multimedia   = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6"
> >
> > meta-boot2qt
> >
> > meta-raspberrypi-extras = "<unknown>:<unknown>"
> >
> > meta-mingw        = "HEAD:1c2e155111dce94423cc227ea69f7f50f316c78e"
> >
> > meta-qt5          = "HEAD:49e9d9a73b5c6e3d6eab88dc0005305e85b1a62d"
> >
> > meta-sakura       = "<unknown>:<unknown>"
> >
> > Initialising tasks: 100%
> >
> |###################################################################
> ##
> >
> |###################################################################
> ##
> > |###|
> > Time: 0:00:00
> >
> > NOTE: Executing SetScene Tasks
> >
> > NOTE: Executing RunQueue Tasks
> >
> > WARNING: linux-raspberrypi-1_4.4.50+gitAUTOINC+04c8e47067-r0
> > do_kernel_configcheck: [kernel config]: specified values did not make
> > it into the kernel's final configuration:
> >
> > ---------- CONFIG_SND_SOC_MAX9768 -----------------
> >
> > Config: CONFIG_SND_SOC_MAX9768
> >
> > From:
> > /home/gwilson/Qt/Qt-5.9.6/Yocto-build-RPi3/build-raspberrypi3/tmp/work
> > -shared/raspberrypi3/kernel-source/.kernel-meta/configs/Scribe.cfg
> >
> > Requested value:  CONFIG_SND_SOC_MAX9768=y
> >
> > Actual value:
> >
> > Config 'SND_SOC_MAX9768' has the following conditionals:
> >
> > Dependency values are:
> >
> > ---------- CONFIG_MAX1363 -----------------
> >
> > Config: CONFIG_MAX1363
> >
> > From:
> > /home/gwilson/Qt/Qt-5.9.6/Yocto-build-RPi3/build-raspberrypi3/tmp/work
> > -shared/raspberrypi3/kernel-source/.kernel-meta/configs/Scribe.cfg
> >
> > Requested value:  CONFIG_MAX1363=m
> >
> > Actual value:     # CONFIG_MAX1363 is not set
> >
> > Config 'MAX1363' has the following conditionals:
> >
> >    I2C (value: "y")
> >
> > Dependency values are:
> >
> >    I2C [y]
> >
> > ---------- CONFIG_CAN_EMS_USB -----------------
> >
> > Config: CONFIG_CAN_EMS_USB
> >
> > From:
> > /home/gwilson/Qt/Qt-5.9.6/Yocto-build-RPi3/build-raspberrypi3/tmp/work
> > -shared/raspberrypi3/kernel-source/.kernel-meta/configs/Scribe.cfg
> >
> > Requested value:  CONFIG_CAN_EMS_USB=m
> >
> > Actual value:     # CONFIG_CAN_EMS_USB is not set
> >
> > Config 'CAN_EMS_USB' has the following conditionals:
> >
> >    (none)
> >
> > Dependency values are:
> >
> > Here is my
> >
> > linux-raspberrypi_4.4.bbappend for the kernel:
> >
> > # Scribe additions to Kernel configuration
> >
> > FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
> >
> > FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/${PN}:"
> >
> > SRC_URI += "file://Scribe.scc <file:///%5C%5CScribe.scc>"
> >
> > SRC_URI += "file://mcp251x.c.patch <file:///%5C%5Cmcp251x.c.patch>"
> >
> > The Scribe.scc file:
> >
> > # Scribe additions to kernel configuration
> >
> > kconf hardware Scribe.cfg
> >
> > And the Scribe.cfg file:
> >
> > # Scribe additions to kernel configuration
> >
> > # Enable MAX9768
> >
> > #CONFIG_SOC_ALL_CODECS=m
> >
> > #CONFIG_COMPILE_TEST=y
> >
> > CONFIG_SND_SOC_MAX9768=y
> >
> > # Enable MAX11606
> >
> > #IIO=y
> >
> > CONFIG_MAX1363=m
> >
> > # Enable EMS CPC-USB
> >
> > CONFIG_CAN_EMS_USB=m
> >
> > Here is my directory tree:
> >
> > Qt-5.9.6
> >
> >       Yocto-mirror
> > # Yocto build mirror
> >
> >       Yocto-build-RPi3                                              #
> > Yocto build root
> >
> >                  build-raspberrypi                                   #
> > build directory
> >
> >                  sources
> >   # yocto sources
> >
> >                         meta-sakura
> > # our recipes
> >
> >                                 recipes-kernel
> > # directory for kernel changes
> >
> >                                         linux
> >     # directory that contains linux-raspberrypi_4.4.bbappend
> >
> >                                                files
> >       # directory that contains .scc & .cfg files
> >
> > As seen above none of the changes are accepted although there is
> > nothing that blocks any of them.
> >
> > Any help understanding this would be greatly appreciated.
> >
> > Regards,
> >
> > Greg Wilson-Lindberg
> >
> >
> >

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

[-- Attachment #1.2: Type: text/html, Size: 14406 bytes --]

[-- Attachment #2: bblayers.conf --]
[-- Type: application/octet-stream, Size: 377 bytes --]

# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/gwilson/Qt/poky/meta \
  /home/gwilson/Qt/poky/meta-poky \
  /home/gwilson/Qt/poky/meta-yocto-bsp \
  /home/gwilson/Qt/poky/meta-raspberrypi \
  /home/gwilson/Qt/poky/meta-test \
  "

[-- Attachment #3: local.conf --]
[-- Type: application/octet-stream, Size: 10297 bytes --]

#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.

#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for
# demonstration purposes:
#
#MACHINE ?= "beaglebone"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86 if no other machine is selected:
MACHINE ??= "raspberrypi2"

#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
#DL_DIR ?= "${TOPDIR}/downloads"

#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
#SSTATE_DIR ?= "${TOPDIR}/sstate-cache"

#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
#TMPDIR = "${TOPDIR}/tmp"

#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "poky"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"

#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
#  - 'package_deb' for debian style deb files
#  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
#  - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"

#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"

#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
#  "dbg-pkgs"       - add -dbg packages for all installed packages
#                     (adds symbol information for debugging/profiling)
#  "dev-pkgs"       - add -dev packages for all installed packages
#                     (useful if you want to develop against libs in the image)
#  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
#                     (useful if you want to run the package test suites)
#  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
#  "tools-debug"    - add debugging tools (gdb, strace)
#  "eclipse-debug"  - add Eclipse remote debugging support
#  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
#  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
#  "debug-tweaks"   - make an image suitable for development
#                     e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"

#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
#   - 'buildstats' collect build statistics
#   - 'image-mklibs' to reduce shared library files size for an image
#   - 'image-prelink' in order to prelink the filesystem image
#   - 'image-swab' to perform host system intrusion detection
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"

#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. To
# enable this uncomment this line. See classes/testimage(-auto).bbclass for
# further details.
#TEST_IMAGE = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"

#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS ??= "\
    STOPTASKS,${TMPDIR},1G,100K \
    STOPTASKS,${DL_DIR},1G,100K \
    STOPTASKS,${SSTATE_DIR},1G,100K \
    STOPTASKS,/tmp,100M,100K \
    ABORT,${TMPDIR},100M,1K \
    ABORT,${DL_DIR},100M,1K \
    ABORT,${SSTATE_DIR},100M,1K \
    ABORT,/tmp,10M,1K"

#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"


#
# Qemu configuration
#
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"

# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"

[-- Attachment #4: meta-test.tar --]
[-- Type: application/x-tar, Size: 10240 bytes --]