summaryrefslogtreecommitdiffstats
path: root/meta/recipes-rt
Commit message (Collapse)AuthorAgeFilesLines
* rt-tests: update to 0.83Koen Kooi2011-11-041-6/+10
| | | | | | | | | Fetch from github, kernel.org uri is gone (From OE-Core rev: e3c003282afb93ec52882496400b042620ab00ef) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rt-tests: use an explicit commit IDDarren Hart2011-08-121-1/+2
| | | | | | | | | | Using a tag, like v0.73, forces network access to resolve a commit ID. Use the corresponding commit ID in the recipe. (From OE-Core rev: d126e22f6b3f27196144f87e22b36ebccd6dea65) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes-rt: add a README documenting the contents of recipes-rtDarren Hart2011-08-121-0/+13
| | | | | | | | | Document the non-obvious bits of using the recipes-rt recipes. (From OE-Core rev: 2c86e636972bd02b35523b36bc81a2765f430f70) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Move meta-rt recipes to oe-core (meta)Darren Hart2011-08-123-0/+49
Keeping the rt recipes in their own layer has led to maintenance issues, particularly with the linux-yocto-rt recipes. As these kernel types are part of the same linux-yocto source repository, it seems reasonable to include the rt kernel recipes alongside the standard recipes. A new recipes-rt directory for the other recipes provides adequate separation and eliminates the need for a separate layer. As there is no meta-rt/conf/layer.conf to force the kernel, users must now specify the rt kernel in their local.conf or in the machine.conf: PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" The merging of the rt recipes into the core also eliminates complications with multiple layer dependencies for new BSP layers. Having to either separate RT BSPs from standard BSPs or force users to add meta-rt to bblayers even when not building an RT BSP (because the RT BSPs in the same layer would fail to parse without it) was sub-optimal at best. (From OE-Core rev: bafaaad264fe3e745c714951ddcf2784d33b755a) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OpenPOWER on IntegriCloud