openembedded-core.git/meta/recipes-kernel/kern-tools, branch danny

kernel-yocto: fix kernel configuration audit for custom yocto kernels

2012-09-14T08:49:55+00:00

It was reported that the kernel configuration checks for custom yocto
kernels had the following output:

  NOTE: validating kernel configuration
  grep: /meta-series: No such file or directory
  grep: /meta-series: No such file or directory
  WARNING: Can't find any BSP hardware or required configuration fragments.
  WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
  NOTE: Tasks Summary: Attempted 375 tasks of which 367 didn't need to be rerun and all succeeded.

which is not inspire confidence in the output of the process.

Completely inhibiting the check is one option to remove the messages,
but that removes the ability see output, which can help move users to
a better or more fully configured linux-yocto based kernel.

To fix this, we have to ensure that the path to the meta-series is
always valid, and that the tools can deal with not all files existing
in the audit directory.

Since custom yocto kernels do not set KMETA (they don't have a meta branch),
we ensure that a default of 'meta' is passed to the audit ('meta' is always
valid), and that kconf_check itself can deal with an incomplete set of
input audit files.

The net result is output like this (using a defconfig with invalid options
for the kernel being built):

  NOTE: validating kernel configuration
  This BSP sets 19 invalid/obsolete kernel options.
  These config options are not offered anywhere within this kernel.
  The full list can be found in your kernel src dir at:
  meta/cfg/standard/qemux86/invalid.cfg

  There were 1 instances of config fragment errors.
  The full list can be found in your kernel src dir at:
  meta/cfg/standard/qemux86/fragment_errors.txt

  The full list can be found in your kernel src dir at:
  meta/cfg/standard/qemux86/missing_required.cfg

Signed-off-by: Bruce Ashfield 
Signed-off-by: Saul Wold

kern-tools: fix non-inheriting branch names

2012-09-04T13:45:23+00:00

Importing the following tools SRCREV:

    kgit-meta: exclude explicit branches from name calculations

    kernel branches are constructed during patching of the tree by
    constructing a '/' based hierarchy of names as each branch
    directive is encountered.

    But if a "branch $name $branchpoint" is used, the entire branch
    name is supplied so no additions to the hierarchy should
    happen. As such, that type of branch command should not be part
    of branch name calculation and preparation.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

linux-yocto: fix unapplied patch error message

2012-09-04T13:45:09+00:00

When patches fail to apply, the status of all pending patches should
be exported to the logs and to the user. Currently, a missing export
of GUILT_BASE makes it look more like an internal error, than a 'normal'
patch failure:

    | [ERROR] unable to complete push
    | pending patches are:
    | Patches directory doesn't exist, try guilt-init

With this variable exported, we have this:

  | [INFO] validating against known patches  (qemux86-standard-meta)
  | error: patch failed: Makefile:2
  | error: Makefile: patch does not apply
  | To force apply this patch, use 'guilt push -f'
  | [ERROR] unable to complete push
  | pending patches are:
  | links/files/0002-makefile-patch.patch

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

kern-tools: fix forced branching

2012-09-04T13:45:00+00:00

commit 7a79f7412 [linux-yocto: make KBRANCH the exception and not the rule]
ensures that a request branch is always built. The implementation of this
guarantee is a branch switch before the build starts. But that switch may
be before all patches are applied. If the proper routines are not called,
no patches can be applied to the tree.

Updating the SRCREV to pickup this fix:

    updateme: use branch command when forcing branch switches

    When forcing a branch switch to the desired branch we should be
    using the proper 'branch' command. Since without this call, the
    proper variables will not be set, and patches can't be applied
    to the tree.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie

kernel-yocto: set master branch to a defined SRCREV

2012-08-25T13:44:01+00:00

To support custom repositories that set a SRCREV and that only have
a single master branch, do_validate_branches needs a special case
for 'master'. We can't delete and recreate the branch, since you
cannot delete the current branch, instead we must reset the branch
to the proper SRCREV.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Saul Wold

kern-tools: fixes (branching,buildall) + cleanups (checkpoint,cleaner)

2012-08-19T09:33:17+00:00

Updating the kern-tools SRCREV to pickup a collection of bug fixes
and cleanups:

  75e71c3 kgit-config-cleaner: add -k 
  02be3b5 buildall: switch back to scc driven processing
  c7101db kern-tools: support flexible branching
  e2d06bd kern-tools: Remove superfluous references to "defconfig" from the "createme" script.
  e693754 kgit-checkpoint: fix verify_branch variable name typo
  ee67a7b kgit-config-cleaner: fix redefintion processing

Signed-off-by: Bruce Ashfield 
Signed-off-by: Saul Wold

linux-yocto: explicitly export KMETA to scripts

2012-08-19T09:33:08+00:00

The kern-tools scripts can support a meta branch and directory of a name that
isn't "meta", but they need the name passed through the environment variable
KMETA. ensuring that KMETA is exported in the shell environment sets the stage
to support flexible meta branch name.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Saul Wold

linux-yocto: make KBRANCH the exception and not the rule

2012-08-19T09:32:46+00:00

The kernel branch is no longer required by the yocto-kern-tools
to locate BSP feature descriptions (it is the MACHINE:KTYPE
descriptor), so we no longer require that the BSP branch be
explicitly set.

If a kernel branch is explicitly set, it is now used to trigger
a checks to ensure that the branch really is being built.
Otherwise the branch that the machine description creates will
be built (just as it always was).

This further simplies the use and configuration of a linux-yocto
based kernel recipe.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Saul Wold

kern-tools: add buildall and robustness fixes

2012-06-28T15:23:16+00:00

Updating the kern-tools SRCREV to pickup the following functionality:

 - buildall: provides the ability to build all kernel branches
             without a build system, only a cross compiler and configme
             are required.

 - robustness/cleanups: obselete/unused code removal and general robustness
                        fixes from Paul Gortmaker and Bruce Ashfield

The following kern-tools commits are part of this series:

 b8dfd3d buildall: add whitelist/blacklist support
 0ef039c configme: catch errors found during fragment sanitization
 5b6498c buildall: remove all instances of it using/reading scc files
 2e57550 buildall: support semi seamless restarts
 4b5dd4d kconf_check: simplify cmdline args, dont store data per branch
 58fbb6e configme: relieve it of all knowledge of scc files
 a03e291 configme: strip out alternative meta series logic.
 96d2bcf kgit-init: check for valid branchpoint
 5598db6 buildall: allow a max cap on the number of builds done
 b46abec buildall: add support for randomizing build order
 68a04e9 buildall: dont copy failed build logs into main build dir
 5575d85 buildall: script to independently build all board kernels
 86d6200 configme: delete unused variable
 8d4e29d configme: delete unused KPROFILE setting
 7e15436 configme: ensure we have a valid machine type set
 152b9cb scc: remove depreciated/unused commands
 bb4e96a scc: allow includes within conditional statements
 7da7951 configme: derive path to tools from $0
 152dc45 configme: test for BUILD_DIR != ""
 129f7b0 kgit-scc: add warnings about bad input args.
 e977662 kgit-scc: add text for no arg and invalid arg case.

[YOCTO #843]

Signed-off-by: Bruce Ashfield

kern-tools: anchor KMACHINE test

2012-06-08T10:56:21+00:00

Updating the kern-tools SRCREV to pick up the following fix:

    Out of tree feature descriptions (.scc files) take two forms: normal
    features and BSP descriptions.

    A normal feature is detected and added to the end of the current machine
    being processed. During tree processing, it's configuration and patches
    will be applied.

    A BSP description on the other hand must be matched based on three
    critera (which are in the .scc file via "define "):

      - machine
      - kernel type
      - architecture

    Since features that define machines are only explicitly added, they
    are removed from the list of features that should be automatically
    added.

    The criteria for removing them from the auto-add list is the
    definitions found in the .scc file. The existing check was simply
    for KMACHINE anywhere in the file. This meant that a conditional
    or even a comment containing that phrase would exclude a file.

    Properly anchoring the KMACHINE test to "^define.*KMACHINE" fixes the
    problem of overly agreesive exclusions.

Signed-off-by: Bruce Ashfield 
Signed-off-by: Richard Purdie