On 16-02-12 08:42 PM, California Sullivan wrote:
The developer ktype enables EMBEDDED, EXPERT, and DEBUG_KERNEL,
opening up more kernel options and setting some defaults.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
ktypes/developer/developer.cfg | 19 +++++++++++++++++++
ktypes/developer/developer.scc | 10 ++++++++++
2 files changed, 29 insertions(+)
create mode 100644 ktypes/developer/developer.cfg
create mode 100644 ktypes/developer/developer.scc
diff --git a/ktypes/developer/developer.cfg b/ktypes/developer/developer.cfg
new file mode 100644
index 0000000..ee04ec7
--- /dev/null
+++ b/ktypes/developer/developer.cfg
@@ -0,0 +1,19 @@
+#.........................................................................
+# WARNING
+#
+# This file is a kernel configuration fragment, and not a full kernel
+# configuration file. The final kernel configuration is made up of
+# an assembly of processed fragments, each of which is designed to
+# capture a specific part of the final configuration (e.g. platform
+# configuration, feature configuration, and board specific hardware
+# configuration). For more information on kernel configuration, please
+# consult the product documentation.
+#
+#.........................................................................
+
+#
+# General setup
+#
+CONFIG_EXPERT=y
+CONFIG_EMBEDDED=y
+CONFIG_DEBUG_KERNEL=y
diff --git a/ktypes/developer/developer.scc b/ktypes/developer/developer.scc
new file mode 100644
index 0000000..7ab51de
--- /dev/null
+++ b/ktypes/developer/developer.scc
@@ -0,0 +1,10 @@
+# Include this kernel type fragment to get the standard features and
+# configuration values, as well as EXPERT, EMBEDDED, DEBUG_KERNEL,
+# and the options defaulted to yes through them.
+
+include ktypes/standard/standard.scc
I'm thinking that a comment right here in the .scc file might be
appropriate.
To explain why in the "developer" kernel, we are creating a branch
called standard. i.e. for compatibility reasons .. or looking at
it more closely, do we need the branch statement here at all ?
ktypes/standard/standard.scc should be taking care of it.
Bruce
+branch standard
+
+force kconf non-hardware developer.cfg
+
+include features/debug/debug-kernel.scc
--
_______________________________________________
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto