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

linux-yocto: kernel configuration cleanups

2011-09-22T02:07:37+00:00

There were some config fragment warnings that were being hidden
by virtue of being output while generating the full config versus
the ones that were generated during the configuration audit task.

This change does the following:

  - Updates the kern-tools SRCREV to include changes that move
    all kernel configuration warnings to the audit script

  - Updates the meta SRCREV for linux-yocto to get updated
    kernel configuration fragments that are warning-free. These
    are duplicated configs, and other changes that have a net
    result of no runtime changes.

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

linux-yocto: generalize kernel config search pattern

2011-09-05T19:24:55+00:00

After constructing a kernel configuration file it then needs
to be located in the tree so it can be audited against the
final .config. The previous string that was used for the search
pattern contains the kernel version. If the recipe space kernel
version and internal tree version are out of sync, this will
cause the constructed config to not be found. By removing the
version from the search string, we can still find out config and
gracefully adapt to minor version skew.

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

kern-tools: allow flexible branch points

2011-08-24T22:13:55+00:00

Updating the SRCREV to pickup a series of changes to the
kern-tools that allow more flexible creation of trees from
scratch. This functionality is not used by the normal
kernel build process and has no impact on existing builds.

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

linux-yocto: allow configuration of arbitrary branches

2011-08-08T12:38:53+00:00

When building an external tree or bootstrapping a BSP the
external branch may not have been checked out. The tools now ensure
that the tree is ready for configuration, so we no longer need to
force the checkout of the external branch.

This change is coupled with some kern tools tweaks as follows:

  40d9bab updateme: allow the location of board descriptions based on defines
  59859ca createme: use branch name when creating meta data
  91b4275 configme: determine meta branch based on directories, not branch naming
  f5a915c kgit-meta: make branch creation and renaming more robust

Signed-off-by: Bruce Ashfield

kern-tools: update SRCREV

2011-07-22T10:48:11+00:00

Fixes [YOCTO #1261]

Updating the SRCREV to pickup some branch creation fixes that
were causing an invalid branch name to be used on a repository
that couldn't support it (i.e. standard/base on a 2.6.34).

With this the 2.6.34 and 3.0 -rt branches will build.

Signed-off-by: Bruce Ashfield

linux-yocto: detect and avoid branch revision checking for AUTOREV

2011-05-17T13:38:52+00:00

When a BSP or layer specifies an AUTOREV for SRCREV, the logic
that matches expected vs real branch heads doesn't apply. We
always want the latest.

To solve the issues with invalid git revs causing validation
failures, we detect the AUTOINC value and do a early return,
skipping validation.

Signed-off-by: Bruce Ashfield

kern-tools: error if features are not found

2011-05-13T05:04:18+00:00

Fixes bug: [YOCTO #955]

Updating the SRCREV to pickup the kern-tools change:

[
    updateme: error if features are not found

    Rather than silently dropping addon features, we emit a warning
    and then exit with a failure code. The caller can then abort a
    build and not simply miss features.

    Passing --no-strict to the script disables this new functionality
    if for some reason a feature description is missing on purpose.
]

Signed-off-by: Bruce Ashfield

linux-yocto: error if meta data not present

2011-05-10T08:51:55+00:00

There are valid reasons to build repositories without meta
data present and there are times when this is an error. This
change adds sanity tests to the build process to detect missing
meta data and throw an informative error message.

Sanity checking is only triggered from recipes (linux-yocto)
that always require meta data to be present. Other recipes
are not impacted and can auto-generate meta data as required.

Without this change the build process suceeds, but incorrect
meta data will be used (with no user knowledge), which is not
the desired behaviour.

Signed-off-by: Bruce Ashfield

linux-yocto: safely process unbranched repositories

2011-05-05T10:54:47+00:00

The BSP bootstrap and -dev use cases can be applied against
unbranched or repos without meta data. To allow the proper
and safe processing of those repositories, slight modifications
to the tools are required to pass the branch on the command
line (rather than detecting it always) and to only checkout
branches that exist.

Signed-off-by: Bruce Ashfield

linux-yocto: apply meta data to external repos

2011-05-05T10:54:47+00:00

To support quick uprev and testing, it is desireable to build
repositories that do not have embedded meta data. In this scenario
the meta data can be automatically created or provided externally.
This commit supports the first situation by detecting the lack
of meta data and then automatically creating a base set of meta
files.

Signed-off-by: Bruce Ashfield