4801 2013-07-02 09:10:58 +0000 [mpc8315e-rdb] u-boot version warning when building image 2013-07-05 03:28:39 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-yocto 1.4 x86 Multiple RESOLVED INVALID Undecided normal --- 1 yi.zhao bruce.ashfield ke.zou ning.zhang yi.zhao --- --- --- oldest_to_newest 34270 0 yi.zhao 2013-07-02 09:10:58 +0000 Git rev: master/80b263430453896189b704d0997943642eec6fef When building mpc8315e-rdb images, I got the following warning message: ################ NOTE: preferred version v2012.04% of u-boot not available (for item u-boot) NOTE: versions of u-boot available: v2011.03+gitAUTOINC+19b54a7018 v2011.06+gitAUTOINC+b1af6f532e v2013.01.01+gitAUTOINC+e8ae0fa5ed NOTE: preferred version v2012.04% of u-boot not available (for item u-boot) NOTE: versions of u-boot available: v2011.03+gitAUTOINC+19b54a7018 v2011.06+gitAUTOINC+b1af6f532e v2013.01.01+gitAUTOINC+e8ae0fa5ed NOTE: preferred version v2012.04% of u-boot not available (for item u-boot-dev) NOTE: versions of u-boot available: v2011.03+gitAUTOINC+19b54a7018 v2011.06+gitAUTOINC+b1af6f532e v2013.01.01+gitAUTOINC+e8ae0fa5ed ################# There is no u-boot_2012.04.bb in meta/recipes-bsp/u-boot directory. But in meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf, the u-boot preferred version is 2012.04: PREFERRED_VERSION_u-boot ?= "v2012.04%" And it will use 2011.06 instead of 2012.04. 34343 1 bruce.ashfield 2013-07-05 02:59:09 +0000 We have no plans to uprev the uboot support for this reference board. I indicated on the mailing list when this was mentioned, the old version works, and there's no reason to continually update firmware. 34345 2 yi.zhao 2013-07-05 03:26:38 +0000 Someone upgraded the u-boot from 2012.04.01 to 2013.01.01 with poky commit: 228cced04d9f25f10d089ddd97592077362f60bf. Before the upgrading, the 2012.04.01 also works fine with this bsp. 34346 3 bruce.ashfield 2013-07-05 03:28:39 +0000 I realize that someone removed it, when it was mentioned, I said the same thing "the reference BSP is using it, so don't remove it". The point is that whoever removed it, should have checked the BSP and updated it, not the reference BSP.