<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-intel.git/conf/machine/include, branch dizzy</title>
<subtitle>[no description]</subtitle>
<id>https://git.enea.com/cgit/linux/meta-intel.git/atom?h=dizzy</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-intel.git/atom?h=dizzy'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/'/>
<updated>2014-10-21T20:50:37+00:00</updated>
<entry>
<title>intel-microcode: Add ability to filter microcode</title>
<updated>2014-10-21T20:50:37+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2014-10-01T01:23:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=a3a380373b3f47df90f0c585ce9b071f80b216c9'/>
<id>urn:sha1:a3a380373b3f47df90f0c585ce9b071f80b216c9</id>
<content type='text'>
The microcode data file released by Intel has microcode for many Intel
processors, which by default all get installed onto the target image.
In some situations it may desirable to choose microcode for only a
selected processor or processors.  This change provides an easier way
to filter and select only the microcode of interest for BSPs from
recipe space.

A new variable, UCODE_FILTER_PARAMETERS, is introduced, which can be
defined to contain parameters to the iucode_tool which will filter the
microcode of interest for the BSP under consideration.  More
information on the iucode-tool parameters is available here:
http://manned.org/iucode-tool.

This filtering makes the generated microcode files very
machine-specific, hence making the recipe machine-specific. BSPs using
the common Intel kernel will not be using the filtered microcode, and
will be able to share the intel-microcode packages with the common
Intel package arch for the recipe.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Acked-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel: Add new intel-ucode MACHINE_FEATURE</title>
<updated>2014-10-21T19:34:20+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2014-09-17T16:45:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=c64ade471ab70860604db2ade19ec6cfe9504f50'/>
<id>urn:sha1:c64ade471ab70860604db2ade19ec6cfe9504f50</id>
<content type='text'>
With this change, Intel microcode support can be enabled or disabled
for any BSP by controlling the MACHINE_FEATURES variable.

Any BSP from the meta-intel layer can enable Intel microcode loading
support by adding the following line in the machine configuration.

  MACHINE_FEATURES += "intel-ucode"

This change keeps the intel-microcode feature disabled by default; it
can however be enabled as an "opt-in" feature via the MACHINE_FEATURES
variable.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel.inc: Use LTSI kernel for poky-lsb images</title>
<updated>2014-10-21T17:28:13+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2014-10-16T22:17:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=c32b5938039830875e931340492cfd7dc6f57a77'/>
<id>urn:sha1:c32b5938039830875e931340492cfd7dc6f57a77</id>
<content type='text'>
v3.10 is now the latest LTSI kernel.  Use it for all the poky-lsb
images, so that it gets validation in the QA cycles.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Remove all the changes related to the proprietary EMGD graphics driver</title>
<updated>2014-09-17T01:12:28+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2014-09-04T22:55:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=c939705c186388df1eb68341a207fb2c6ac95f66'/>
<id>urn:sha1:c939705c186388df1eb68341a207fb2c6ac95f66</id>
<content type='text'>
As all the EMGD based BSPs have been retired, there is no need for the
proprietary EMGD support in the meta-intel layer.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel BSPs: enable microcode loading support for images</title>
<updated>2014-09-04T13:46:42+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2014-06-18T01:10:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=50abd223b626fc7508e24b55fc1b22c7b3a66e97'/>
<id>urn:sha1:50abd223b626fc7508e24b55fc1b22c7b3a66e97</id>
<content type='text'>
For the BSPs using the meta-intel.inc file enable the early boot-time kernel
as well as the user space microcode loading support.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Tom Zanussi &lt;tom.zanussi@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>meta-intel.inc: Enable ASPEED Tech Graphic Card</title>
<updated>2014-05-09T16:25:26+00:00</updated>
<author>
<name>Ong Boon Leong</name>
<email>boon.leong.ong@intel.com</email>
</author>
<published>2014-03-26T09:55:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=0462a27791664f702e605dadbb279b2b61883b2c'/>
<id>urn:sha1:0462a27791664f702e605dadbb279b2b61883b2c</id>
<content type='text'>
This is to enable ASPEED Technology graphic card
that is bundled inside certain Intel customer reference
board.

Signed-off-by: Ong Boon Leong &lt;boon.leong.ong@intel.com&gt;
Acked-By: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
</content>
</entry>
<entry>
<title>intel-common: Set common PACKAGE_ARCH for linux-yocto-rt</title>
<updated>2014-04-09T16:51:19+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2014-04-01T22:34:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=db84acfc8d9ed8dccd4a79de39fee337bc729662'/>
<id>urn:sha1:db84acfc8d9ed8dccd4a79de39fee337bc729662</id>
<content type='text'>
The linux-yocto/meta support is now available for the intel-core*
machines and the preempt-rt kernel. Enable the common PACKAGE_ARCH in
intel-common-pkgarch.inc.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>intel-common-pkgarch: Correct PACKAGE_EXTRA_ARCHS usage</title>
<updated>2014-02-21T08:53:52+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2014-02-21T08:47:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=d7026654ae4d18e7d7c193f64e4a4ce22453cfa5'/>
<id>urn:sha1:d7026654ae4d18e7d7c193f64e4a4ce22453cfa5</id>
<content type='text'>
The trailing S was missing from the variable name, resulting in
the kernel-modules package not being found as the common arch was not
added to the PACKAGE_ARCHS variable used by the package manager.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>intel-common: Make using intel-common override opt-in</title>
<updated>2014-02-06T04:43:54+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2014-02-06T03:15:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=c7bf6a327b9b9ebb982324c6ef9f595f7a14f94a'/>
<id>urn:sha1:c7bf6a327b9b9ebb982324c6ef9f595f7a14f94a</id>
<content type='text'>
Currently the intel-core*-common.inc files also include the
intel-common-pkgarch.inc, forcing the introduction of the intel-common
PACKAGE_ARCH. Coupling this with the addition of the intel-common
MACHINE_OVERRIDE, means that even MACHINE_ARCH packages can be
influenced by intel-common overrides, which is not desirable.

Remove the intel-common-pkgarch.inc from the intel-core*common.inc
include files, requiring BSPs wanting to use the intel-common mechanism
to explicitly include it. This obviates the need to reset the
linux-yocto PACKAGE_ARCH to MACHINE_ARCH.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Cc: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>MACHINEOVERRIDES: Use INTEL_COMMON_PACKAGE_ARCH</title>
<updated>2014-02-06T04:42:00+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2014-02-03T23:23:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=dd0bd45aa410929d0af1be63ab7397fa40148c41'/>
<id>urn:sha1:dd0bd45aa410929d0af1be63ab7397fa40148c41</id>
<content type='text'>
Create the intel common override for use in currently machine-specific
recipes which need to make overrides for all the compatible machines,
such as COMPATIBLE_MACHINES in the linux-yocto* recipes.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
</feed>
