aboutsummaryrefslogtreecommitdiffstats
path: root/bsp/intel-common/intel-core2-32-preempt-rt.scc
AgeCommit message (Collapse)Author
2019-10-07meta: add SPDX License Identifier and updates 00-README with License policyYann CARDAILLAC
Signed-off-by: Yann CARDAILLAC <ycnakajsph@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
2019-01-23intel: drop branch directiveBruce Ashfield
We don't need a branch to have different machines/bsps and configurations. We aren't carrying any patches on these branches at the moment, so suspending them until they are needed again keeps clutter down in the trees. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-09-07intel-common: add intel-developer-drivers.scc to preempt-rt BSPsCalifornia Sullivan
Since we include the developer ktype we should include developer drivers. Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2016-05-26intel: Use standard/preempt-rt/intel branchTom Zanussi
We now have a dedicated standard/preempt-rt/intel branch for Intel platforms, so have the core meta-intel BSPs make use of it. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2015-03-05intel-common: split out 32 bit common-driversSaul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-10-10intel: Remove the standard ktype nestingDarren Hart
Fixes [YOCTO 6710] intel-common-standard.scc included the standard ktype, but the preempt-rt scc files included intel-common-standard and the preempt-rt ktype. This resulted in a double include of the standard ktype, which caused the meta/scripts/updateme to change the source tree from standard/preempt-rt/base to standard/standard/preempt-rt and drop all the preempt-rt commits. To address this, avoid the nested inclusion of ktypes by explicitly including them in each top level BSP definition. Remove the ktype from intel-common-standard.scc and rename it intel-common-drivers.scc, which more accurately describes its purpose anyway. Update the top the BSPs to use the new name and explicitly include the required ktype. Remove some obsolete comments and clean-up the whitespace in the top-level BSP scc files a bit. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Bruce Ashfield <bruce.ashfield@windriver.com> -- Please apply to linux-yocto-3.14 and to 3.17 after reverting: intel: create intel-common-preempt-rt and use it Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-10-10Revert "intel: create intel-common-preempt-rt and use it"Bruce Ashfield
This reverts commit 1d86365fb6548d2eae089910b22bda683ae27746.
2014-09-08intel: create intel-common-preempt-rt and use itBruce Ashfield
The -preempt variants were including intel-common-standard.scc, and then the preempt-rt kernel type. But since preempt-rt also includes the standard kernel, this results in a double include of the standard kernel, at a different point in the branch structure, and hence a less than obvious branch is created like: standard/standard/preempt-rt. To fix this, we create a parallel intel-common-preempt-rt and include it when necessary. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
2014-05-20meta: rearrange intel-core2-32-preempt-rt includesTom Zanussi
Having standard follow ktypes/preempt-rt/preempt-rt.scc means that settings in standard take precedence, which isn't the expected behavior. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
2014-04-02intel-common: Add preempt-rt ktype targetsDarren Hart
Add the preempt-rt ktype scc targets for the intel-core2-32 and intel-corei7-64 BSPs. These are also the intel-common configuration used for all intel-common compatible BSPs. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>