kern-tools: remove unused code, meta branch and directory assumptions

Updating the kern-tools SRCREV to pick up fixes that remove unused
code, transition code (tree format changes) and to remove assumptions
about branch and directory naming.

There are no user visible changes with this update, but the plumbing
changes will be used in future updates for more generalized support.

The commit details are below:

 Author: Bruce Ashfield <bruce.ashfield@windriver.com>
 Date:   Fri May 11 12:13:12 2012 -0400

    kgit-publish: remove --remote option

    The ability to publish and automatically push a repository was
    never used, and is error prone. The complexit isn't needed in
    the script, so removing it is the best option.

    An explicit push after tree publication is suggested, or a
    wrapper script (specific to a particular infrastructure) around
    this script.

    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

 Author: Bruce Ashfield <bruce.ashfield@windriver.com>
 Date:   Fri May 11 12:04:09 2012 -0400

    kern-tools: remove unused code, scripts and transition code

    The period of supporting old trees with a different meta
    branch name and directory structure are gone. So the cleanup
    and removal of the old structure can be completed.

    The meta branch and directory are now controlled via command line,
    or via the KMETA environment variable. No testing and conditional
    processing of the tree are required.

    Additionally, the generate_cfg script is no longer used, or is the
    branch conditing code in createme. So they can be safely removed
    from the tools and repository.

    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

 Author: Bruce Ashfield <bruce.ashfield@windriver.com>
 Date:   Thu May 10 12:18:19 2012 -0400

    kern-tools: remove meta tag and directory assumptions

    During repository sanity checks (createme) and during the
    checkpoint process, there were several assumptions about the tree
    that either relied on a tag, or a particular directory name.

    With this set of changes, simply passing the meta branch name is
    enough to sanitize and restore the checkpoint. If no meta branch
    name is passed, the default of 'meta' is used for both the branch
    and meta data directory name.

    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/3.2: update to v3.2.18

Updating the 3.2 kernel SRCREVs to pickup the -stable update
to v3.2.18.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/3.0: update to v3.0.32

Updating the 3.0 kernel SRCREVs to integrate the v3.0.32 -stable
release.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto: remove v2.6.37 recipe

With the introduction of the 3.4 kernel recipe, the 2.6.37 kernel
recipe is removed, keeping the supported list at three kernels.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto: add machine aliases for yocto BSPs

To avoid mapping machine names to kernel machine names in recipes,
we can define multiple KMACHINE names for a single in tree board.
This allows the tools to match a board description to multiple
different MACHINEs.

As a result, we can remove the explicit KMACHINE mappings from
the linux-yocto recipes and allow the KMACHINE=${MACHINE} default
to handle mappings. Individual recipes an bbappends can override
this as required.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto: add 3.4 recipe

Introducing the 3.4 kernel recipe. At this point there are three
supported kernel 3.4, 3.2 and 3.0.

Build and boot tested on qemux86, qemux86-64, qemuarm, qemumips and
qemuppc

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/3.2: fri2 and chiefriver machine updates

Bumping the 3.2 SRCREVs to pickup the following configuration changes for
the new chiefriver BSP and the existing fri2 machines:

 5b4c9dc fri2: update base config
 cdfbb50 fri2: add usb-mass-storage to standard and preempt-rt
 3c1af06 fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi feature
 26a4d79 iwlagn: Correct a comment typo
 ade9c57 iwlwifi: Add a feature for iwlwifi
 571b6cb fri2: Configuration update (usb, wifi, i2c)
 b257485 meta: add tmp/rc6 feature
 24c6494 chiefriver: create initial BSP infrastructure

All branches are also updated with the following fix:

  1ce6700 efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)

Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-yocto/3.0: add cedartrail kernel features

Updating meta to move Kernel Features out of the BSP and add to
the Cedartrail Machine branch.

Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kern-tools: anchor KMACHINE test

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 <foo>"):

      - 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 <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>