<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-intel.git/meta-jasperforest, branch dylan</title>
<subtitle>[no description]</subtitle>
<id>https://git.enea.com/cgit/linux/meta-intel.git/atom?h=dylan</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-intel.git/atom?h=dylan'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/'/>
<updated>2013-10-09T19:35:20+00:00</updated>
<entry>
<title>BSP READMEs: change the language of the compliance section</title>
<updated>2013-10-09T19:35:20+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-10-09T18:13:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=7e03eb2132506c40cad685a805783c47c0c209d0'/>
<id>urn:sha1:7e03eb2132506c40cad685a805783c47c0c209d0</id>
<content type='text'>
Use "Yocto Project Compatible" in place of "compliance" as suggested
by Jeffrey Osier Mixon.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>meta-jasperforest: Fix BBFILES</title>
<updated>2013-04-23T13:15:37+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2013-04-23T12:26:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=19740c20016561d691bf1f45e213c45213faafd2'/>
<id>urn:sha1:19740c20016561d691bf1f45e213c45213faafd2</id>
<content type='text'>
BBFILES is whitespace delimited. If .= used, no whitespace padding is added around
the addition and this can lead to it being combined with some other part of the
field, leading to parts of BBFILES mysteriously not being seen.

For example, I have in my bblayers.conf:

  /media/build1/poky/meta-intel/meta-emenlow \
  /media/build1/poky/meta-intel/meta-fri2 \
  /media/build1/poky/meta-intel/meta-jasperforest \
  /media/build1/poky/meta-intel/meta-n450 \
  /media/build1/poky/meta-intel/meta-romley \

and this results in the warning:

WARNING: No bb files matched BBFILE_PATTERN_fri2 '^/media/build1/poky/meta-intel/meta-fri2/'

and if I try to build MACHINE=fri2, I get strange errors due to the .bb files
not being parsed.

The fix is simply to use +=, just like every other layer.conf file.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>linux-yocto-rt_3.8: Update all non-ISG BSPs with rt support to 3.8.4-rt2</title>
<updated>2013-04-05T18:08:39+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2013-04-04T02:36:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=ad3b4d1ad663958c9aa8c17374e42b7d8598bf4c'/>
<id>urn:sha1:ad3b4d1ad663958c9aa8c17374e42b7d8598bf4c</id>
<content type='text'>
Add the linux-yocto-rt_3.8.bbappend for every BSP supporting RT.

Do not update BSPs maintained by ISG.

Built, booted, and sniff tested with:

$ cyclictest -p 90 -D 10m -t

on all platforms. All boot and complete the test without abnormal
outliers with the following exceptions:

o sys940x generated a panic, reported to rt-user. Possibly hw related.
o fri2 fails to boot, hanging at "i8042: No controller found"

These need additional investigation, but shouldn't delay the merge of
the recipes themselves.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>jasperforest: update v3.8 kernel recipe commits to v3.8.4</title>
<updated>2013-03-29T17:41:03+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-03-25T17:43:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=fc9107502d0aed4bb1355f5c57a032476c6e5f42'/>
<id>urn:sha1:fc9107502d0aed4bb1355f5c57a032476c6e5f42</id>
<content type='text'>
And specify the LINUX_VERSION corresponding to the kernel branch commits.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>jasperforest: move BSP to the v3.8 kernel</title>
<updated>2013-03-06T21:37:33+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-03-04T20:22:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=b5bd50f2e3a0b9e26eaca7c721b92dcc7a06c6a2'/>
<id>urn:sha1:b5bd50f2e3a0b9e26eaca7c721b92dcc7a06c6a2</id>
<content type='text'>
Now the v3.8 kernel recipes are available in the oecore &amp; meta-intel layers.
And also the v3.8 kernel is validated for this BSP.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>jasperforest: linux-yocto_3.8 recipe extension</title>
<updated>2013-03-06T21:36:33+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-03-02T01:26:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=06a3def2be477f4c47670e1c470fbfcc155ead3d'/>
<id>urn:sha1:06a3def2be477f4c47670e1c470fbfcc155ead3d</id>
<content type='text'>
Provide the jasperforest BSP specific extension for the linux-yocto_3.8
recipe from the oecore layer. This configures the right git branches of
the kernel repository for the jasperforest BSP.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>jasperforest: linux-yocto-dev recipe extension</title>
<updated>2013-03-04T22:53:58+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-02-25T18:53:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=dfbe8372a4b722162c4754e4d37c5d306dd99e19'/>
<id>urn:sha1:dfbe8372a4b722162c4754e4d37c5d306dd99e19</id>
<content type='text'>
Provide the jasperforest BSP specific extension for the linux-yocto-dev
recipe from the oecore layer. This configures the right git branches of
the kernel repository for the jasperforest BSP.

This commit is addressing this bug:
[YOCTO #3931]

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel: remove kernel AUTOREVs</title>
<updated>2013-02-04T16:39:06+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@linux.intel.com</email>
</author>
<published>2013-02-04T16:39:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=575f93dd4ba1fb9aca8a58dc66e9066eca0a3925'/>
<id>urn:sha1:575f93dd4ba1fb9aca8a58dc66e9066eca0a3925</id>
<content type='text'>
Using AUTOREV turns out to cause problems with unreproducible
autobuilder builds and unwanted network access.  This patch removes
kernel AUTOREVs and locks down SRCREVs and LINUX_VERSIONs.

Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>BSP layer READMEs: fix the YP Compliance link</title>
<updated>2013-01-19T22:18:44+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-01-18T05:14:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=d92dd091397b4c77000c2db152bb621a62b76cf9'/>
<id>urn:sha1:d92dd091397b4c77000c2db152bb621a62b76cf9</id>
<content type='text'>
The link has changed on the yoctoproject website, updating the URL
in the BSP layer READMEs.

This fixes the bug:
[Yocto #3730]

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Use .= for adding to BBPATH and += to BBFILES</title>
<updated>2013-01-07T17:59:05+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2013-01-04T03:50:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=227d8fa72c2ffbccee4c21ffb32841129a550729'/>
<id>urn:sha1:227d8fa72c2ffbccee4c21ffb32841129a550729</id>
<content type='text'>
Fixes parsing errors which is appearing after this commit to
meta-openembedded

http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e

This triggers
exception NameError: name 'base_contains' is not defined
without this change

Avoid the immediate expansion operator (:=) which caused base_contains
added in the previous commit to fail to expand at the time the
meta-intel layer configs are parsed and replace it with one of the
append operators (.= or +=) that allows for delayed variable expansion.

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Acked-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
</feed>
