Bug 4801

Summary:	[mpc8315e-rdb] u-boot version warning when building image
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Yi Zhao <yi.zhao>
Component:	bsps-meta-yocto	Assignee:	Bruce Ashfield <bruce.ashfield>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Undecided	CC:	ke.zou, ning.zhang, yi.zhao
Version:	1.4
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Yi Zhao 2013-07-02 09:10:58 UTC

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.

Comment 1 Bruce Ashfield 2013-07-05 02:59:09 UTC

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.

Comment 2 Yi Zhao 2013-07-05 03:26:38 UTC

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.

Comment 3 Bruce Ashfield 2013-07-05 03:28:39 UTC

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.