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

kern-tools: use dylan branch

2013-12-03T16:49:22+00:00

This switches the kern-tools to use the matched dylan branch that is maintained
to work against the dylan release of yocto/oe-core.

As part of this switch, we also update the SRCREV to match the latest fixes for
the dylan kernel-tools.

Signed-off-by: Bruce Ashfield

kern-tools: refresh and make dash compliant

2013-05-22T10:57:46+00:00

The separately packaged merge_config.sh in the kern-tools package was
missing upstream fixes, and in particular a change that ensures it is
dash compatible.

By grabbing that upstream commit and rebasing the existing patches on
top of the new baseline, we are up to date and working on systems
where /bin/sh is dash.

[YOCTO #4473]

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

kern-tools: anchor and delimit regexs

2013-05-20T15:06:21+00:00

Updating the kern-tools SRCREV with the following fix:

    Updateme is responsible for updating an existing meta-series with new patches,
    configs and tree manipulations. To do this, it first checks for an existing
    board description and generates one if required. It then searches for features
    and fragments to be applied for the tree.

    There were two problems:

     - A top level board description is detected via the presence of "define"
       directives that indicate the board name, the arch and kernel type. The
       test for define would match on patches or fragments with 'define' in their
       name, and would incorrectly use that file as the top level board description.

       This is fixed by ensuring that only defines at the start of a line, or preceded
       by whitepace match.

     - When searching for features that were indicated as 'addon' or 'optional', the
       search would find, and apply, any feature with the passed name as substring
       versus an exact match.

       This is fixed by ensuring that the matched feature name is /
       versus 

(From OE-Core master rev: 57ae1e412a35d827f84bf9b1f48747bf703f84b7)

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

kern-tools: fix custom repository BSP generation

2013-04-15T20:15:20+00:00

Updating the SCRCREV to pick up the following fix

    updateme: use absolute path for generated BSP descriptions

    When a custom BSP is used, a top level BSP is generated by the tools and fed
    to the build system just as a user defined BSP would be located and
    passed. The location of the generated file is placed in the top_tgt file,
    which is used by subsequent stages. A relative path was being placed into
    top_tgt, which binds the build to a particular directory structure and
    working directory.

    The location of parts of the build have changed, and this relative path is
    no longer accurate. Changing it to an absolute path solve the build issues
    related to custom BSPs.

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

kern-tools: fix non-local patch/config location

2013-04-12T16:00:13+00:00

A regression was introduced when implementing the ability to restrict
configuration values via include directives. Only patch and config files that
were local to a feature directory could be found. While this doesn't impact
most users of the tools, it is an issue that needs to be fixed.

Additionally, the regex that detected flags passed to includes was not
specific enough, and unfortunately named feature files would match. This
resulted in features like standard-nocfg.scc inhibiting all configuration
items, even base configs.

This change also bumps the linux-yocto 3.4 and 3.8 PR values to ensure
that kernels will be rebuilt once this change is active.

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

kern-tools: fix conditional configuration items

2013-04-11T07:27:27+00:00

Variables defined in .scc files have two purposes:

   - Documentation in the meta-series
   - Variables that can be tested in sub sections and other features

The second part of this functionality was broken when fixing configuration
for tiny/small systems. As a result, arch tests were failing and configs were
dropped.  This restores the existing functionality.

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

kern-tools: fix excluded configuration processing

2013-04-10T16:59:40+00:00

One of the features introduced early on in the 1.4 release cycle was the
ability to include a kernel feature, but only get its patches and not configs
(and vice versa).

As it turns out, this only was exercised recently and once a single include
with dropped configs was started, ALL configuration values following the
commit were dropped.

To fix the problem, the processing of kernel features has been split into
two. Where the features are preprocessed and the assembled/complete file is
used to generate the meta-series (which is later applied to the tree). The
logic of the tools is the same, but the two phases of processing allows
configuration values to be excluded properly and simply, while keeping the
logic for modifying the tree in a separate step.

All changes are invisible to the user, and are done within the existing
scripts and build system bindings. Output series and manipulations to
the tree are the same as they were before this change.

Updating the kern-tools SRCREV to pickup the kern-tools changes for this.

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

kern-tools: initialization and meta branch fixes

2013-03-26T17:48:42+00:00

Bumping the kern-tools SRCREV to pickup the following fixes and documentation
updates:

  d484e3f kgit-meta: remove hardcoded meta directory name
  affad20 yocto-kernel-tools: Typoes, "fragement", "depreciated"
  142ed49 kgit-init: update tools list

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

kern-tools: import configuration, controls and audit updates

2013-03-02T22:43:06+00:00

Updating the kern-tools SRCREV to import the following fixes:

  commit 7f91d198d32fc90260e52724ef4aac0b997c1e8b

    kconf_check: fix new Kconfig detection

    One of the functions of the kernel configuration audit is to notify
    the user if Kconfig* files have been removed from the kernel, and
    also to notify of new Kconfig files.

    New Kconfig files should be classified as hardware or non-hardware to
    allow BSP audits to notify if boards are setting values that they
    shouldn't, hence why notifying about new "buckets" is important.

  commit c4f26a3296e0e1c3dbdd5ec8e2947d5443a9ffc2

    updateme/scc: allow config fragment exclusion

    It is common to need the features (patches, git operations) of a
    branch, but not want the kernel configuration fragments of a given
    branch. To allow this, we provide a new include flag "nocfg".

    When this flag is used, all of the configuration fragments included
    by the targetted feature will not be applied to the current build,
    with one exception, a base/critical fragment can force it's config
    values, since without them, the system would not be functional.

    Example:

       include ktypes/standard/standard.scc nocfg

  commit c7ec19d55aca6c4b17073c5362fce5be61a89d82

    scc: wrap git merge

    To allow for parameter validation and sanity checking, wrap "git merge"
    as a dedicated "merge" command instead of using the raw git fallback.

    This also makes it consistent with existing top level commands such
    as  'tag', 'branch', 'patch', etc.

    There are no changes to arguments, and existing 'git merge' commands
    continue to work with this change.

[YOCTO #3419]
[YOCTO #3421]

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

kernel-yocto: allow multiple / shared kernel feature directories

2013-02-04T13:15:51+00:00

To promote the reuse and sharing of configuration fragments this change
allows any kernel-yocto based recipe to have multiple alternate git repositories
which provide kernel feature directory trees listed on the SRC_URI.

These feature directories are in addition to any in-tree kernel meta data branches
that may be available (described via the KMETA variable in linux-yocto recipes).

Features found within these directories can be used from recipes via the
KERNEL_FEATURES variable. Features found within a feature directory are free
to include any other features that are available in any directories. In both
cases the path to a feature description (a .scc file) is relative to the
root of a given feature directory (which is how existing .scc files work)

The search order for features is determined by the order that repositories
appear on the SRC_URI.

Normal SRC_URI rules apply to any repository that is added as a kernel
feature container. A SRCREV must be supplied and it must be unpacked to
a unique directory, which is controlled via the "destsuffic" url parameter.

In addition to these standard requirements, any kernel feature repository
reference should identify itself via the "type=kmeta" url parameter. If
type=kmeta is not supplied, the repository will not be processed for
kernel features.

As an example, the following in a linux-yocto bbappend makes two additional
feature directories available to KERNEL_FEATURES and fragments.

 SRC_URI += "git://git.yoctoproject.org/yocto-kernel-cache;protocol=git;branch=master;type=kmeta;name=feat1;destsuffix=kernel-cache/"
 SRC_URI += "git://${KSRC_linux_yocto_3_4};protocol=file;branch=meta;name=feat2;type=kmeta;destsuffix=kernel-features-experimental/"

 SRCREV_feat1 = "${AUTOREV}"
 SRCREV_feat2 = "${AUTOREV}"

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