<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta-rt/recipes-kernel/linux-yocto-rt_stablegit.bb, branch uninative-2.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-2.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2011-08-12T16:21:55+00:00</updated>
<entry>
<title>meta-rt: refresh linux-yocto-rt recipe</title>
<updated>2011-08-12T16:21:55+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2011-07-19T22:31:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=897f83efc04af1104ce71baede95de86885ffd3a'/>
<id>urn:sha1:897f83efc04af1104ce71baede95de86885ffd3a</id>
<content type='text'>
Rename the recipe to match the linux-yocto recipe renames using the kernel
version in the PV portion of the filename.

Add the SRCREVs to the recipe as was done with the core linux-yocto recipes.

Add qemux86 as it is also present in the linux-yocto-2.6.34.git repository.

(From OE-Core rev: 6e9e19230ee731856639f71c5adfb01a92f620d8)

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>kernel-rt: use correct branch names and new git SRC_REV format</title>
<updated>2011-04-20T01:18:06+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2011-04-19T23:54:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=cd5e5860669cd7b41e77bfc21a18b7d779b8ab68'/>
<id>urn:sha1:cd5e5860669cd7b41e77bfc21a18b7d779b8ab68</id>
<content type='text'>
The RT kernel recipe was not updated to reflect the new git SRC_REV format nor
to take advantage of the recent updates made to the underlying infrastructure.
These fixes bring it up to date with the other linux-yocto* recipes and fix
various build issues people were seeing.

(From OE-Core rev: 690e87a2ffe8caa16379be26eb356c5bded17c1f)

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Cc: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-rt: atom-pc support</title>
<updated>2011-01-20T21:36:58+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2010-12-28T17:23:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=238c13f10603e3566cbdd79ecc4c358aa9ab9fcc'/>
<id>urn:sha1:238c13f10603e3566cbdd79ecc4c358aa9ab9fcc</id>
<content type='text'>
Add support for the atom-pc machine to the meta-rt layer. This has
been boot tested on the Intel n450 development board (Black Sand).

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
CC: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
CC: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>meta-rt: Initial PREEMPT_RT layer and kernel recipes</title>
<updated>2011-01-20T21:36:58+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2010-12-20T23:02:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=0d7d5666509c013228242b87c1dfd15395af6701'/>
<id>urn:sha1:0d7d5666509c013228242b87c1dfd15395af6701</id>
<content type='text'>
The meta-rt layer provides a preempt_rt kernel recipe
using the linux-yocto-stable git tree. It overrides
the virtual/kernel provider and defines the compatible
machines and per-machine SRCREVs. The initial layer
supports only qemux86-64.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Cc: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Cc: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
</feed>
