Bug 5456

Summary: Consolidate meta-intel BSPs where possible
Product: [Build System, Metadata & Runtime] BSPs Reporter: Darren Hart <dvhart>
Component: bsps-meta-intelAssignee: Darren Hart <dvhart>
Status: VERIFIED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, corneliux.stoicescu, nitin.a.kamble, srifenbark, tom.zanussi
Version: 1.5   
Target Milestone: 1.6 M4   
Hardware: x86   
OS: Multiple   
Whiteboard: 10 April 2014: Setting documentation flag to "Done."
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: Done (doc changes complete)
Bug Depends on:    
Bug Blocks: 5469    

Description Darren Hart 2013-11-04 17:47:59 UTC 
There is a great deal of duplication in the meta-intel BSPs. This is due in part to the nature of the OE BSP definition which differentiates at the board level. With IA, this is often not necessary. This is especially the case with BSPs such as crownbay, fri2, sys940x, and minnowboard, all of which are Queensbay platforms and differ primarily in their default modules and kernel command line arguments.

There are two approaches for consolidation:

1) By platform. e.g. reduce all the Queensbay platforms to a queensbay bsp with instructions for customizing the boot parameters, etc.

2) Leverage the yocto-bsp generic-x86[_64] BSPs wherever possible. These BSPs are intended to run on a broad range of hardware and ultimately should cover nearly all of the supported platforms. The exception here would be for binary drivers, such as EMGD.

There is a potential feature development here for the concept of a "BSP variant" which would allow for finer grained control of configuration options beyond the traditional OE concept of a MACHINE. This could even be a post-image-generation configuration, possibly even an input to the deployment tooling (wic).
Comment 1 Alexandru Georgescu 2013-12-20 10:56:56 UTC 
Hi Darren,
Any update on this? Also, can you update the Target milestone to adjust the QA planning as well.

Thanks!
Comment 2 Darren Hart 2014-03-05 22:07:35 UTC 
Kernel consolidation patches are under test. Various issues are being reported across the BSPs. We are working them. Targeting M4 timeframe.
Comment 3 Darren Hart 2014-04-08 15:31:16 UTC 
This has been completed for the 1.6 releases.

The non-emgd systems have been updated to reuse the INTEL_COMMON_PKGARCH for the linux-yocto kernel.
Comment 4 Scott Rifenbark 2014-04-09 17:54:14 UTC 
I don't believe this affects the YP user manuals.  It might affect README files, etc.  Let me know if there are user doc changes from this fix.  I am leaving the documentation flag alone since it might pertain to other docs.

Scott
Comment 5 Darren Hart 2014-04-09 18:07:37 UTC 
I've added READMEs which are a start. They aren't stellar, but they document the mechanism. I don't believe more is *required*, although things could certainly be improved.
Comment 6 Scott Rifenbark 2014-04-10 17:26:12 UTC 
Hi 

I am marking this doc flag to "Done."

Thanks, 
Scott
Comment 7 Stoicescu Cornel 2014-04-22 07:52:09 UTC 
The affected BSPs are built correctly and work on the designated hardware targets as intended. I also tested the generic intel-core2 and intel-corei7-64 machine targets and they could build. 

Marking this as verified.