linux/poky.git/meta/recipes-bsp/uboot/u-boot_git.bb, branch scarthgap

u-boot: rename u-boot_git.bb to u-boot_${PV}.bb

2011-05-27T15:38:53+00:00

In order to facilitate reuse of the oe-core u-boot recipe, there needs to be some assurance that the oe-core version won't change without a clear indicator to people extending it. By renaming the recipe to include its version string instead of "git", BSP layers can extend a specific base version of u-boot, ie. u-boot_2011.03.bbappend. When 2011.06 becomes available, we can create that file without instantly breaking all the BSPs depending on oe-core version of the recipe. As a matter of policy I would recommend we not carry more than 2 versioned u-boot recipess at any given time. This will provide BSP layers time to migrate to the newer version, without cluttering oe-core with numerous stale versions of u-boot. We may decide later to resurrect u-boot_git.bb as an AUTOREV recipe to faciliate upstream development on u-boot in the oe environment. (From OE-Core rev: f788d4b503ecc6600612746c4936dfb9393e237c) Signed-off-by: Darren Hart Cc: Richard Purdie Cc: Koen Kooi Cc: Jason Kridner Signed-off-by: Richard Purdie

u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINES

2011-05-27T15:38:53+00:00

oe-core does not define any machines, so it does not make sense to add machine specific information in the oe-core u-boot recipe and infrastructure. Also note that COMPATIBLE_MACHINES is not easily extended due to its regex syntax: "(machine_a|machine_b)", making it difficult to extend the u-boot recipe in bbappend files without resorting to machine specific overrides. Remove COMPATIBLE_MACHINES and the default UBOOT_MACHINE from the recipe and insert some anonymous python into u-boot.inc to raise SkipPackage if UBOOT_MACHINE is not set (this ensures 'world' still works for machines that can't build u-boot). UBOOT_MACHINE must now be specified in each machine config that requires u-boot. This is an improvement over requiring machine specific overrides in every BSP layer's u-boot_git.bbappend file. For example, a beagleboard machine config currently contains: UBOOT_ENTRYPOINT = "0x80008000" UBOOT_LOADADDRESS = "0x80008000" With this change, it must now contain: UBOOT_MACHINE = "omap3_beagle_config" UBOOT_ENTRYPOINT = "0x80008000" UBOOT_LOADADDRESS = "0x80008000" So long as the SRC_URI in the base recipe can build a working u-boot for a given machine, there is no need to create a u-boot_git.bbappend file. If additional patches are deemed necessary, a BSP layer creates a u-boot_git.bbappend file and extends the SRC_URI to include general or machine specific backports. Note: I used bb.note() instead of bb.debug() to ensure the message at least makes it to the console. From what I could gather, bb.debug() doesn't go anywhere during recipe parsing. (From OE-Core rev: c7a198d7472b4767047dbbfeecb4d941055262b3) Signed-off-by: Darren Hart Cc: Richard Purdie Cc: Koen Kooi Cc: Jason Kridner Cc: Chris Larson Signed-off-by: Richard Purdie

Revert "u-boot: fix LIC_FILE_CHKSUM"

2011-05-20T16:08:51+00:00

This reverts commit 2d2563a7b003b265b5cdad98588606379e5edd4c. Saul discovered this change was incorrect.

u-boot: fix LIC_FILE_CHKSUM

2011-05-20T11:40:44+00:00

(From OE-Core rev: bbdd81fcd25d2d5aa730a1ea99eecf50a2111989) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

u-boot: update SRCREV to 2011.03

2011-05-19T19:51:38+00:00

Fixes [YOCTO 1029] u-boot 2010.12 fails to run on the Beagleboard C4 and xM Rev A boards. Commit 55aacbc30e48f6f8a73fb989a58625e70887bc01 suggests there was a mixup during development, as the MD5SUM change is from the 2011.03 SRCREV back to the 2010.12. Chances are a patch was never sent to update the SRCREV, leaving the MD5SUM in a bad state. Update the SRCREV and COPYING MD5SUM to use the 2011.03 version. Built and tested on Beagleboard xM Rev A and Beagleboard Rev C4. (From OE-Core rev: 68d301e950c06eda8c8a73db1ed299c45dee7b9f) Signed-off-by: Darren Hart Tested-by: Jeff Osier-Mixon Cc: Jeff Osier-Mixon Cc: Yi Zhao Cc: Robert Berger Cc: Gary Thomas Merged Richard's removal of PR from PV Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

u-boot: Don't add PR in PV, its pointless

2011-05-19T19:48:29+00:00

(From OE-Core rev: 2f597ad74d7ed383365dba10e61010e8f82ab6b1) Signed-off-by: Richard Purdie

u-boot: correct COPYING MD5SUM

2011-05-09T13:09:10+00:00

(From OE-Core rev: d0dc2b5bb02ef55a41e7a97b6831c72391ae7f36) Signed-off-by: Darren Hart Signed-off-by: Richard Purdie

poky-default-revisions: move the SRCREV to recipe file

2011-05-04T14:06:36+00:00

in this case, those non poky distro can also use these recipe normally (From OE-Core rev: 0a57bd226cdb8332707fa0f46fcf0b067f03701a) Signed-off-by: Yu Ke Signed-off-by: Richard Purdie

u-boot: remove do_install from u-boot.inc

2011-03-01T17:59:55+00:00

Fixes [BUGID #777] The do_install rule in u-boot.inc was installing a host tool into the target ${bindir}, which is subsequently stripped with target strip during packaging, and the obvious error ensues. The native u-boot recipe has its own install rule, and the machine specific u-boot doesn't require mkimage or anything else in the do_install function. So we remove it completely until it is needed again. [sgw: PR bump] Signed-off-by: Bruce Ashfield Signed-off-by: Saul Wold

uboot: move license data into recipe with SRC_URI

2011-02-09T22:44:52+00:00

The LIC_CHKSUM_FILES are specific to the source determined by SRC_URI. As such, keep all the license information together with the SRC_URI. This also avoids confusion from having these defined in both the .inc and the .bb files. The CHKSUM got out of date in u-boot_git.bb, so update it while we're at it. Signed-off-by: Darren Hart CC: Ilya Yanok CC: Gary Thomas CC: Richard Purdie