| Age | Commit message (Collapse) | Author |
|---|
|
In order to use the full do_configure in the existing linux kernel recipe
infrasturcture, use linux.inc rather than just the kernel bbclass. This
ensures the defconfig is copies to .config, the recipe fails to build without
this change.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
do_unpack_append() was being treated as a Python function, so the syntax was
wrong. By using that function to run a shell function, the problem is solved.
Patterned this after similar functions, e.g. in the eglibc recipe.
Proposed-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Make the meta-linaro more consistent with other layers and fix a an issue
where all the recipes were not being matched by BBFILES.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The git fetcher changes in master (Feb 2 2011) require SRC_URI updates
to the bbappend files.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
What is it ?
------------
A gathering place for extensions to the linux-yocto (or really
any) kernel recipes that faciliate the creation and development
of kernel features, BSPs or configuration.
What does it do?
----------------
Currently this is mainly additions to the kernel recipes to:
- Use a local clone vs a remote clone
- Use AUTOREV to track the HEAD of branches vs a specific revision
- Ensure that the $MACHINE is compatible with the yocto kernel
- disables branch/revision checking
- controls the naming of the linux build dirs via BB_LOCALCOUNT_OVERRIDE
and LOCALCOUNT
What will be added to it ?
--------------------------
- Tools specifically related to kernel development if they are
unique and don't belong in the main layers.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Saul Wold <sgw@linux.intel.com>
|
|
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
These recipes are created by using linaro gcc source code and existing gcc
recipes in the poky.
Rebased patches to the linaro gcc code:
These two patches needed rebasing, as some of the code form these patches
is already in the linaro tree code.
gcc-4.5.linaro/gcc-flags-for-build.patch
gcc-4.5.linaro/gcc-poison-system-directories.patch
change the version to 4.5.1.linaro:
Change the version to 4.5.1.linaro as it reflects the linaro's gcc
source tree's version correctly.
New Patch:
change_base_version_to_4.5.1.linaro.patch
This is a new patch to reflect the change in the version in the BASE_VER in the
source code; more documentation in the patch.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
|
|
Introduce the meta-linaro layer with an initial skeleton including the recipe
for linux-linaro-2.6.35:
dvhart@fear:~/source/poky.git/meta-linaro$ tree
.
|-- TODO
|-- conf
| |-- layer.conf
| `-- machine
| `-- beagleboard-linaro.conf
`-- recipes-kernel
|-- linux-linaro-2.6.35
| `-- beagleboard-linaro
| `-- defconfig
`-- linux-linaro-2.6.35_git.bb
The general approach to using this layer is to add the layer to bblayers.conf
and to set MACHINE to a *-linaro machine from those added by this layer. For now
you can build the existing images, such as poky-image-minimal. We may add linaro
specific images as we flesh out the recipe.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
Darren Hart
Nitin A Kamble
Bruce Ashfield
Saul Wold