<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-intel.git/conf/machine/include, branch daisy-enea-man</title>
<subtitle>[no description]</subtitle>
<id>https://git.enea.com/cgit/linux/meta-intel.git/atom?h=daisy-enea-man</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-intel.git/atom?h=daisy-enea-man'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/'/>
<updated>2014-04-09T16:51:19+00:00</updated>
<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>
<entry>
<title>meta-intel.inc: Use X86 instead of IA32</title>
<updated>2014-01-28T00:56:13+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2014-01-22T04:52:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=2929967d15a3078d1d4cfd71336a5447b5fd77d3'/>
<id>urn:sha1:2929967d15a3078d1d4cfd71336a5447b5fd77d3</id>
<content type='text'>
To be consistent with the renaming in oe-core, use X86 instead of IA32
in the XSERVER_X86* variables.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add Intel core2 and corei7 BSPs and tune files</title>
<updated>2014-01-28T00:56:13+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2014-01-03T21:10:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=45582cbb1cb9a6ea4f803405159fb08a03c72bea'/>
<id>urn:sha1:45582cbb1cb9a6ea4f803405159fb08a03c72bea</id>
<content type='text'>
Introduce two new generic BSPs that parallel the updated core2 and new
corei7 tune files in oe-core. These BSPs provided optimized tune flags
for Intel Core and Atom CPUs since 2006 in the 32 bit core2 BSP and since
Nehalem and Silvermont (Bay Trail) in the 64 bit corei7 BSP.

These establish a suitable balance between compatibility and performance
optimization.

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Cc: Richard Purdie &lt;richard.purdie@intel.com&gt;
Cc: Paul Eggleton &lt;paul.eggleton@intel.com&gt;
Cc: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Cc: Nitin Kamble &lt;nitin.a.kamble@intel.com&gt;
Cc: Mark Hatle &lt;mark.hatle@windriver.com&gt;
Cc: Bruce Ashfield &lt;bruce.ashfield@windriver.com&gt;
</content>
</entry>
<entry>
<title>meta-intel-emgd.inc: specify preferred providers for gl components</title>
<updated>2013-09-18T13:14:41+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2013-09-17T19:44:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=7b5023275b887851b145abfc38474dbbd328d89c'/>
<id>urn:sha1:7b5023275b887851b145abfc38474dbbd328d89c</id>
<content type='text'>
By default the gl components are coming from mesa recipe. But for
BSPs with EMGD graphics, these components come from emgd and
mesa-gl recipes.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
</content>
</entry>
<entry>
<title>Separate packagedir for GL components of EMGD BSPs</title>
<updated>2013-09-18T13:13:06+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2013-09-16T14:56:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=49f495e388d986e568f6197075a56a6e7674b2f5'/>
<id>urn:sha1:49f495e388d986e568f6197075a56a6e7674b2f5</id>
<content type='text'>
When multiple BSPs of the same arch are built in a build directory,
the differences in GL providers such as emgd-driver and mesa causes
rebuild of large set of recipes, as they collide on each other's space
for multiple BSPs. Although this does not impact correctness, it
impacts build performance negatively.

 Richard had an idea of providing separate PACKAGE_DIR to the
colliding recipes to avoid the build area collision. And this approach
significantly reduces the negative impact on the build performance.

Signed-off-by: Nitin A Kamble &lt;nitin.a.kamble@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-intel.inc: fix xorg packaging issue for emgd BSPs</title>
<updated>2012-12-03T17:33:03+00:00</updated>
<author>
<name>Nitin A Kamble</name>
<email>nitin.a.kamble@intel.com</email>
</author>
<published>2012-12-01T01:49:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=b4141a6404fa7d3445d660860b6bf68acec9f114'/>
<id>urn:sha1:b4141a6404fa7d3445d660860b6bf68acec9f114</id>
<content type='text'>
  BSPs using emgd graphics stack need to use older version
of xserver. And these older xserver recipes still use modules which need
to be specified in the meta-intel.inc.
  This is needed in addition to Ross's xorg packaging fixes in oecore.

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.inc: remove xaa from matrox XSERVER variable</title>
<updated>2012-11-29T23:21:16+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2012-11-29T23:21:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-intel.git/commit/?id=b7337857ca740266d2b067e8c89f82e130825a4b'/>
<id>urn:sha1:b7337857ca740266d2b067e8c89f82e130825a4b</id>
<content type='text'>
XAA has been dropped, so we need to drop the xaa module.

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
</content>
</entry>
</feed>
