Bug 8772

Summary: review, audit and restructure the kytpes available in the yocto-kernel-cache
Product: [Build System, Metadata & Runtime] BSPs Reporter: Saul Wold <sgw>
Component: bsps-configurationAssignee: California Sullivan <california.l.sullivan>
Status: RESOLVED FIXED QA Contact: Costin <costin.c.constantin>
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, bruce.ashfield, jianxun.zhang, yp.bsp.watcher, yp.watcher
Version: unspecified   
Target Milestone: 2.1 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: Yes (doc changes required)

Description Saul Wold 2015-12-04 16:58:16 UTC 
Currently we have a small number of ktypes available for use, they are:

Base
Standard 
  - includes Base
Prempt-RT
  - includes Standard
Tiny
  - includes Standard

We should review and restructure these ktypes to allow for more flexibility and less overlap.

A key example of this flexibility is to allow for disabling a feature that might be enabled in the base or standard .cfg file, such as CONFIG_EMBEDDED. Ideally this would be in an embedded.cfg as an example.

Enabling CONFIG_DEBUG_KERNEL in base.cfg would be another example, while developers might want this enabled, the final production version may want a non-debug kernel for higher security.

These are a couple of examples, but a review of the overlap and items that might be desired by a development kernel vs production kernel would be valuable.

I would expect a very small number of additions (1-3) ktypes.
Comment 1 California Sullivan 2016-02-10 22:21:13 UTC 
This is being worked on in conjunction with bug 8177.

A new ktype is likely to be added with a name such as "devel". This ktype will enable EMBEDDED, EXPERT, DEBUG_KERNEL, and several debug features that are enabled by DEBUG_KERNEL. The base ktype will no longer have these options. A purposed set of changes has been submitted to the linux-yocto mailing list and is currently under discussion.
Comment 2 California Sullivan 2016-03-08 21:16:17 UTC 
This has been integrated into the yocto-kernel-cache and SRCREVs are staged in -next.