https://wiki.yoctoproject.org/wiki/index.php?action=history&feed=atom&title=Wind_River_Kernel 2026-04-18T18:53:13Z Revision history for this page on the wiki MediaWiki 1.39.5 https://wiki.yoctoproject.org/wiki/index.php?title=Wind_River_Kernel&diff=117&oldid=prev 2010-10-22T22:26:28Z

<p>Created page with &#039;The Wind River Linux kernel is a git repository that represents a set of validated/supported and approved set of kernel changes and configuration. == Structure == The Wind Ri…&#039;</p> <p><b>New page</b></p><div>The Wind River Linux kernel is a git repository that represents a set <br /> of validated/supported and approved set of kernel changes and <br /> configuration.<br /> <br /> == Structure ==<br /> <br /> The Wind River Kernel repository is composed of base topic branches, BSP topic branches, and a common<br /> configuration branch.<br /> <br /> A BSP branch contains patches that are specific to a particular board that are either in development<br /> or for technical reasons are not safe for application to all boards via a base topic branch. BSP branches<br /> reference particular configurations that are part of the configuration branch. BSP topic branches have<br /> the convention of &lt;bsp name&gt;-&lt;kernel type&gt;<br /> <br /> Base topic branches are collection points for common features (and configuration) that are safe<br /> for all boards. These are also known as &quot;kernel type&quot; branches. Examples are the &#039;standard&#039; or<br /> &#039;preempt_rt&#039; kernel type branches. BSPs are directly branches from the end of the common topic<br /> branches.<br /> <br /> The configuration branch is called &quot;wrs_meta&quot; and it contains the configuration (And patches) that<br /> are used to create the tree, and configure BSPs. <br /> <br /> The branches in the kernel repository are constructed to be history clean, segmented and <br /> represent the base set of validated and supported board and feature configurations.<br /> <br /> The Wind River kernel recipe has the ability to build arbitrary branches and configurations, so while the<br /> default set of branches are suggested, they are not the only available build targets in the tree.<br /> <br /> == Patching ==<br /> <br /> kernel patching is controlled via the kern_tools and guilt. It is not currently implemented, but<br /> will be available shortly. <br /> <br /> *kernel patching is not encouraged, since accepted changes should be merged directly nto the kernel repository, not patches into the tree*<br /> <br /> == Kernel features ==<br /> <br /> Named kernel features, which are kernel patches and configuration, can be passed to the kernel<br /> recipe and used to modify, configure and manipulate the repository. This functionality is currently<br /> disabled pending standardization on search paths.<br /> <br /> <br /> == Configuration ==<br /> <br /> Configuration of a BSP is done using configuration data captured inside the kernel repository on the <br /> wrs_meta branch. This captured configuration is composed of config fragments that allow common <br /> functionality to be named and grouped. This means that imposing a single change to any BSP is a<br /> one line update to a single file.<br /> <br /> === config fragments ===<br /> <br /> If the default configuration for a BSP needs to be augmented, a kernel configuration fragment<br /> can be created and added to the SRC_URI.<br /> <br /> * file://my_config.cfg<br /> <br /> Will propagate a configuration fragment (which uses the format of any kernel defconfig) to the<br /> workdir, and will be applied to the kernel, and used as the last configuration fragment. Thus<br /> allowing the addition or override of built in configuration values.<br /> <br /> === defconfigs ===<br /> <br /> If building a BSP that is not already merged/defined by the kernel repository, and<br /> entire defconfig can be supplied via the SRC_URI.<br /> <br /> When the defconfig is detected, it will be added to the dynamically created &lt;machine name&gt;-&lt;kernel type&gt; <br /> branch and used as the only configuration for the board.<br /> <br /> == Submitting Changes ==<br /> <br /> Changes are managed using upstream best practices. Pull requests can be sent against<br /> a BSP (or common) branch, and configuration changes against wrs_meta.</div>

Scottrif