<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-intel.git/meta-n450/ReleaseNotes, branch jethro</title>
<subtitle>[no description]</subtitle>
<id>https://git.enea.com/cgit/linux/meta-intel.git/atom?h=jethro</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-intel.git/atom?h=jethro'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/'/>
<updated>2014-03-27T03:41:49+00:00</updated>
<entry>
<title>Remove chiefriver, sys940x &amp; n450 BSPs</title>
<updated>2014-03-27T03:41:49+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2014-03-12T19:12:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=8d79fb4e0cec07fe05ca440578414eaa6be80a3a'/>
<id>urn:sha1:8d79fb4e0cec07fe05ca440578414eaa6be80a3a</id>
<content type='text'>
Configuration for the chiefriver, sys940x, sys940x-noemgd, n450 BSPs are
deleted. The consolidated BSPs viz intel-corei7-64 and intel-core2-32
support these boards.

As part of the usual retirement process, a heads-up email was sent to the
meta-intel mailing list requesting any feedback regarding retirement of
these BSPs. The community did not had any concerning feedback to
reconsider the retirement decision.

The MAINTAINERS file and the layer version of the meta-intel layer are
updated to reflect removal of the BSPs.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
CC: Darren Hart &lt;dvhart@linux.intel.com&gt;
Reviewed-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel: add Patches section to BSP READMEs</title>
<updated>2011-12-01T17:57:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2011-12-01T17:48:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=e742a76993d01b4b8799a0a853c4e533bce955be'/>
<id>urn:sha1:e742a76993d01b4b8799a0a853c4e533bce955be</id>
<content type='text'>
Based on community input, it might be more user-friendly to have some
basic information about submitting patches in the BSP README itself.

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel: update READMEs with layer dependency list</title>
<updated>2011-11-21T15:30:00+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2011-11-21T04:48:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=68c6b19d623b34a504090ad2c706859ecc946256'/>
<id>urn:sha1:68c6b19d623b34a504090ad2c706859ecc946256</id>
<content type='text'>
Add a new 'Dependencies' section listing all the layer dependencies
for each BSP.

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>meta-n450: add dependency info</title>
<updated>2011-06-14T21:43:04+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2011-06-14T18:49:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=129773b573a4a2cf1dff2b0f128a8948c069aca8'/>
<id>urn:sha1:129773b573a4a2cf1dff2b0f128a8948c069aca8</id>
<content type='text'>
Add information on the dependencies needed to use the meta-n450 layer.

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
<entry>
<title>meta-n450: Add new BSP for BlackSand / n450</title>
<updated>2011-01-04T00:46:14+00:00</updated>
<author>
<name>Saul Wold</name>
<email>sgw@linux.intel.com</email>
</author>
<published>2011-01-03T23:33:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=158f88d76685da4e71a21f3788d519dd4b2bb912'/>
<id>urn:sha1:158f88d76685da4e71a21f3788d519dd4b2bb912</id>
<content type='text'>
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
</content>
</entry>
</feed>
