> On their own, the DPDK packages are useless as the user needs to compile
> their application with them. What you're basically doing is forcing a
> library onto
> *every* image for that machine, even ones that don't want to use DPDK.
> Please don't do that.
So, reading from your feedback, I thi
Hi Nitin,
Yes, it can be utilized in crystalforest, highlandforest and mohonpeak.
Thanks and Regards,
-Sreeju
-Original Message-
From: Kamble, Nitin A
Sent: Thursday, September 18, 2014 12:04 AM
To: Selvaraj, Sreeju ArmughanX; meta-intel@yoctoproject.org
Subject: Re: [meta-intel] [PATC
On 9/17/14, 12:58 PM, "Hart, Darren" wrote:
>On 9/17/14, 12:44, "Kamble, Nitin A" wrote:
>
>>From: Nitin A Kamble
>>
>>Some of the platforms supported by the intel-corei7-64 BSP have AMT
>>feature
>>on the platform. Enable it so that it can get utilized with this BSP.
>
>How does this impact
On Tue, 2014-09-16 at 09:27 -0500, Tom Zanussi wrote:
> On Tue, 2014-09-16 at 11:35 +, Stuart Weaver wrote:
> > Hi all,
> >
> > I've just made a fresh Yocto/meta-intel repository and created an
> > image based on core-image-sato for valleyisland-32. However when
> > booting, the kernel was pan
>
>
>
>The problem with this of course is we can't use it easily with the common
>BSPs and ultimately we want to eliminate as many of the other BSPs as
>possible.
>
>What is the exact issue with microcode? How does it break certain systems
>when enabled on the intel common BSPs?
1st there is no bo
On 9/17/14, 13:23, "Kamble, Nitin A" wrote:
>
>>
>>No, we had this discussion. These BSPs need to build out of the box
>>without special flags to disable feature that would otherwise break it on
>>supported systems. If Microcode can't be enabled generically and safely,
>>then it needs to be opt-i
>
>No, we had this discussion. These BSPs need to build out of the box
>without special flags to disable feature that would otherwise break it on
>supported systems. If Microcode can't be enabled generically and safely,
>then it needs to be opt-in, not opt-out.
>
>--
>Darren
We discussed this a bi
On 16 September 2014 12:35, Stuart Weaver wrote:
> I've just made a fresh Yocto/meta-intel repository and created an image based
> on core-image-sato for valleyisland-32.
What release or git revision of poky/yocto/oe-core are you using? The
microcode support in git master of meta-intel needs som
On 9/17/14, 12:44, "Kamble, Nitin A" wrote:
>From: Nitin A Kamble
>
>As per request from Tom, allow disabling of the Intel microcode
>feature for meta-intel BSPs.
>
>If one adds this line to local.conf while build a meta-intel BSP,
>the microcode feature will be disabled for the build target.
>
On 9/17/14, 12:44, "Kamble, Nitin A" wrote:
>From: Nitin A Kamble
>
>Some of the platforms supported by the intel-corei7-64 BSP have AMT
>feature
>on the platform. Enable it so that it can get utilized with this BSP.
How does this impact boot of systems without AMT support? 32 and 64 bit?
>
>S
>>
>
>I agree with Tom here - microcode should be opt-in at the machine level.
>
>Ross
Then it can be implemented as a MACHINE_FEATURE. Tom¹s need is bit
different though. He want it kind of a distro feature, so that poky-tiny
will not pick it up.
Nitin
>
--
___
Tom,
There is an issue with this commit. I will send another commit for this
purpose.
Thanks,
Nitin
On 9/17/14, 12:44 PM, "Kamble, Nitin A" wrote:
>From: Nitin A Kamble
>
>As per request from Tom, allow disabling of the Intel microcode
>feature for meta-intel BSPs.
>
>If one adds this line
On 17 September 2014 20:44, wrote:
> As per request from Tom, allow disabling of the Intel microcode
> feature for meta-intel BSPs.
>
> If one adds this line to local.conf while build a meta-intel BSP,
> the microcode feature will be disabled for the build target.
>
> DISABLE_INTEL_MICROCODE = "1
From: Nitin A Kamble
These commits add
1. AMT feature in the intel-corei7-64 BSP
2. ability to disable the Intel microcode feature
Thanks,
Nitin
The following changes since commit 1796fac0f9baaa056e31559a3c6f5e5b0a8eb743:
Remove the xserver-xorg-1.9.3 recipe and it's files (2014-09-16 20:12:
From: Nitin A Kamble
Some of the platforms supported by the intel-corei7-64 BSP have AMT feature
on the platform. Enable it so that it can get utilized with this BSP.
Signed-off-by: Nitin A Kamble
---
conf/machine/intel-corei7-64.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Nitin A Kamble
As per request from Tom, allow disabling of the Intel microcode
feature for meta-intel BSPs.
If one adds this line to local.conf while build a meta-intel BSP,
the microcode feature will be disabled for the build target.
DISABLE_INTEL_MICROCODE = "1"
Signed-off-by: Nitin A
On Fri, 2014-09-05 at 19:46 -0700, nitin.a.kam...@intel.com wrote:
> From: Nitin A Kamble
>
> These commits remove the proprietary EMGD based BSPs and all the supporti
> needed for these from the meta-intel layer.
>
Pulled into meta-intel/master.
> Thanks,
> Nitin
>
> The following changes si
On 17 September 2014 15:20, wrote:
> Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support
> for romley machiine, so that dpdk will be enabled by default
> for Romley. Also included the dpdk example package, so that
> user can use example apps to exercise the DPDK libraries.
I went thro
Hi Sreeju,
Aren¹t there other BSPs such as crystalforest which can utilize the DPDK
feature?
Nitin
On 9/17/14, 7:20 AM, "sreeju.armughanx.selva...@intel.com"
wrote:
>From: Sreeju Selvaraj
>
>Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support
>for romley machiine, so that dpdk wil
From: Sreeju Selvaraj
Added MACHINE_EXTRA_RRECOMMENDS to include dpdk v1.7.0 support
for romley machiine, so that dpdk will be enabled by default
for Romley. Also included the dpdk example package, so that
user can use example apps to exercise the DPDK libraries.
Signed-off-by: Sreeju Selvaraj
From: Sreeju Selvaraj
Added support for DPDK v1.7.0
Added PACKAGECONFIG mechanism to explicitly disable the use of fuse
and qat which are dependancies for example apps dpdk_qat and vhost.
Added config variables CONFIG_EXAMPLE_DPDK_QAT and
CONFIG_EXAMPLE_DPDK_VHOST to enable or disable the compi
From: Sreeju Selvaraj
Added include file dpdk.inc to share the common functionality
based on dpdk_1.6.0r2
Added a new variable EXAMPLE_BUILD_DIR. this points to apps build
directory which is different in dpdk v1.6.0r2 and v1.7.0.
User of dpdk.inc has to define EXAMPLE_BUILD_DIR for the
installat
From: Sreeju Selvaraj
Hi All,
This series of patches consists below:
1. Upgraded the DPDK to the latest version v1.7.0
2. Added an include file based on the recipe for dpdk_1.6.0r2
3. Cherry picked patches to fix the test case failure of example app
ring_pmd_autotest
4. Cherry picked patch
23 matches
Mail list logo
