https://trygvis.io/git/2012/05/openembedded-core.git/atom?h=master 2011-03-01T11:46:41Z 2011-03-01T11:46:41Z Beth Flanagan elizabeth.flanagan@intel.com 2011-02-24T22:34:59Z urn:sha1:926560497bef54a06a39850fcf551c5c1bba9bfc Removing Emenlow from poky core as it is now in meta-intel as a BSP layer [BUGID #769] Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com> 2011-02-14T13:33:19Z Saul Wold sgw@linux.intel.com 2011-02-14T13:30:59Z urn:sha1:ebe2a5d8d3e412c651ea347fa7d369912589acab Signed-off-by: Saul Wold <sgw@linux.intel.com> 2011-02-14T13:33:19Z Saul Wold sgw@linux.intel.com 2011-02-14T13:30:18Z urn:sha1:c600ea7bac40c8e861541339848a274a98c38eb2 Fixes [BUGID #716] Signed-off-by: Saul Wold <sgw@linux.intel.com> 2011-01-25T12:25:46Z Dongxiao Xu dongxiao.xu@intel.com 2011-01-18T08:19:00Z urn:sha1:6dc67915365d8455c22a411e231e71a72814b889 After machine specific sysroot is implemented, emenlow and atom-pc could build together as one architecture. Thus change emenlow architecture back to core2. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> 2010-12-23T14:20:50Z Tom Zanussi tom.zanussi@intel.com 2010-12-20T18:24:36Z urn:sha1:eca21e63590c165c5aaf14cbd51c7f325b731aba This modifies the meta-emenlow BSP layer to reflect the new BSP standard layout as defined in the latestYocto BSP Developer's Guide. There's no change in functionality here - this simply moves things around, adds a README, and makes the SRCREVs local. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> 2010-12-13T06:23:56Z Bruce Ashfield bruce.ashfield@windriver.com 2010-12-13T06:23:56Z urn:sha1:69ad383525657b44dc7eeb347e888deebb501b00 During the last phase of the recipe factoring, the board compatibility lists ended up in the wrong place, which meant we had an incomplete list of boards, and the same set of boards for both kernels (stable and devel). To fix this, I've yanked the compatibility to the recipes themselves and updated the emenlow to have a -stable bbappend. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> 2010-12-11T06:01:36Z Bruce Ashfield bruce.ashfield@windriver.com 2010-11-18T21:09:02Z urn:sha1:0e7d9956a0cbe95cfe2919d13fcfcac705c4b104 In order to extend and create more kernel recipes based on the supported yocto kernel common routines need to be placed in re-usable blocks. To accomplish this meta/recipes-kernel/linux/linux-yocto_git.bb is broken into three parts: - meta/classes/kernel-yocto.bbclass: contains common routines for checking out and configuring a yocto kernel git repository. This should be inherited by recipes that need this functionality. - meta/recipes-kernel/linux/linux-yocto.inc: Contains the machine mappings, compatibility, build directives and common task definitions for a yocto kernel based recipe. This inherits kernel-yocto, and is the typical point of entry for other recipes. - meta/recipes-kernel/linux/linuux-tools.inc: tasks and function definitions for kernel recipes that want to build/export perf It also updates the linux-yocto recipe to default to 2.6.37. As part of the update to 2.6.37 the branch naming and conventions have been modified to show inheritance, and be more generic. For example: master meta yocto/base yocto/standard/arm_versatile_926ejs yocto/standard/base yocto/standard/beagleboard yocto/standard/common_pc/atom-pc yocto/standard/common_pc/base yocto/standard/common_pc_64 yocto/standard/fsl-mpc8315e-rdb yocto/standard/intel_atom_z530 yocto/standard/intel_core_qm57_pch yocto/standard/mti_malta32_be yocto/standard/preempt_rt/base yocto/standard/preempt_rt/common_pc yocto/standard/preempt_rt/common_pc_64 yocto/standard/preempt_rt/intel_atom_z530 yocto/standard/preempt_rt/intel_core_qm57_pch yocto/standard/qemu_ppc32 yocto/standard/routerstationpro In this structure: master: tracks the mainline kernel meta: meta information for the BSPs and kernel features yocto/base: baseline kernel branch yocto/standard/base: 'standard' kernel, contains features and configs for all BSPs yocto/standard/<machine>: represents a BSP with specific features or configurations The tools, tree and libc-headers have all been updated to deal with this new structure. Also in addition to dealing with the new structure, they continue to work with the existing tree and will adapt at runtime to the differences. The linux-yocto-stable_git.bb recipe continues to build the 2.6.34 based tree,and linux-yocto_git.bb builds 2.6.37. As boards are enabled for the new kernel they will move from -stable to the development kernel. As of now, only the emulated targets have moved to 2.6.37-rcX Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> 2010-12-09T16:18:17Z Saul Wold sgw@linux.intel.com 2010-12-08T04:06:29Z urn:sha1:3d08b9f2c65835822b1c0ed30e3170f02f877ce3 Signed-off-by: Saul Wold <sgw@linux.intel.com> 2010-11-21T01:11:15Z Saul Wold Saul.Wold@intel.com 2010-11-21T01:10:04Z urn:sha1:bd3b63179ccdb030dbf0ff1e792b896f0e1476ae Signed-off-by: Saul Wold <Saul.Wold@intel.com> 2010-11-18T21:30:22Z Bruce Ashfield bruce.ashfield@windriver.com 2010-11-15T16:25:58Z urn:sha1:c70816cb9022dfedd78817bb1dfe20219fe2dd90 The existing preferred yocto kernel wasn't named appropriately and needs to be updated. In keeping the changes small and isolated, this commit simply renames the recipe and some internal variables. Future commits will refactor the code into more usable blocks. Now that linuy-wrs has been renamed linux-yocto, we need to rename and update an board configurations and append files. Now that linux-wrs has been renamed linux-yocto, we need to update the SRCREVs to have the new name. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>