CaROS/meta-intel
3
0
Fork 0
mirror of git://git.yoctoproject.org/meta-intel synced 2026-01-01 13:58:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

meta-crystalforest: add in clarity around how to pick the right QAT version

Browse Source 
Add explanation on how to override the default setting under crystalforest.conf
on PREFERRED_PROVIDER_virtual/qat.

Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
(cherry picked from commit 3577c351cd)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
This commit is contained in:
Ong Boon Leong 2015-07-24 07:48:37 +08:00 committed by Darren Hart
parent 11cbe728ec
commit c1cf5b2b61
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
meta-crystalforest/README
View File

@ -204,12 +204,37 @@ Note:
qat16 recipe is meant for platform with Coleto Creek chipset. qat16 recipe is meant for platform with Coleto Creek chipset.
qat15 recipe is meant for platform with Cave Creek chipset. qat15 recipe is meant for platform with Cave Creek chipset.
conf/machine/crystalforest.conf is the common machine configuration
to support Crystal Forest/server, Crystal Forest/gladden, Highland Forest and
River Forest. In order to generate the right binary for these platforms which
have different QAT technology, user could change the default config accordingly
within crystalforest.conf as below:
For Coleto Creek chipset:
PREFERRED_PROVIDER_virtual/qat ?= "qat16"
For Cave Creek chipset:
PREFERRED_PROVIDER_virtual/qat ?= "qat15"
Another option and preferred approach for above setting is to override
configuration under build/conf/local.conf as follow:
For Coleto Creek chipset:
PREFERRED_PROVIDER_virtual/qat = "qat16"
For Cave Creek chipset:
PREFERRED_PROVIDER_virtual/qat = "qat15"
By default, the machine configuration does not assume that the above By default, the machine configuration does not assume that the above
ingredients are pre-installed onto the BSP. Developers are required ingredients are pre-installed onto the BSP. Developers are required
to either use smart tool to install those software packages or to either use smart tool to install those software packages or
configure IMAGE_INSTALL under build/conf/local.conf, for example. configure IMAGE_INSTALL under build/conf/local.conf, for example.
For Coleto Creek chipset:
IMAGE_INSTALL += "dpdk qat16 zlib-qat" IMAGE_INSTALL += "dpdk qat16 zlib-qat"
For Cavecreek Creek chipset:
IMAGE_INSTALL += "dpdk qat15 zlib-qat"
The list of packages can be searched under tmp/deploy/<package-type> The list of packages can be searched under tmp/deploy/<package-type>
folder. folder.