| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To ease development on unreleased BSPs, let the kernel SRCREV float.
This avoids constantly having to update the SRCREVs manually, and
assures we won't get into a situation where LINUX_VERSION doesn't
match the version set by the kernel recipe.
We'll lock down the kernel SRCREVs and set the matching LINUX_VERSION
when we do releases, but in the meantime, we can use AUTOREV.
Note that individual BSPs are always free to override this maintain
their own SRCREVs if they want to.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
| |
Add Instructions on how to get the DPDK and
QuickAssist Recipes.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
| |
Add Instructions to build the custom Image to
enable qat modules.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
| |
The WEBTITLE will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
|
|
| |
Update all the linux-yocto .bbappends with the latest kernel SRCREVs
and add explicit LINUX_VERSIONs for the 1.3 release, to prevent a
mismatch between the kernel version actually used in the machine
branch vs the version the recipe uses for the kernel image, which can
change with stable updates.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
|
|
| |
Change the Machine names for the two machines
that will be used to publish the BSP on the Yocto
Project website. And add the Yocto Project Compliance
information for the 1.3 release.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
| |
To the latest meta and kernel version (was 3.4.9, now 3.4.11).
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
| |
This adds the two new modules zlib-qat-mem and openssl-qat-mem
modules to build with the custom Image.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
| |
Update SRCREVs of meta branch to include the
new PCI config options added.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replaces all uses of PRINC with the form:
PRINC := "${@int(PRINC) + N}"
Where N is the previously assigned value plus one to ensure a
monotonically increasing PRINC value.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Tom Zanussi <tom.zanussi@intel.com>
CC: Saul Wold <sgw@linux.intel.com>
CC: Nitin Kamble <nitin.a.kamble@intel.com>
|
|
|
|
|
|
|
|
| |
To build with the corpus files recipes, create a customized
recipe to install them into the Image.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
| |
The xserver-xf86-config .bbappends are still using FILESPATH - update
them to use FILESEXTRAPATHS as recommended by the Poky Reference
Manual and BSP Developer's Guides.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
| |
Add a new recipe Silesia Corpus for testing with another
Data Compression algorithm for Crystal Forest BSP.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
|
|
|
|
|
| |
Add a new recipe for Crystal Forest BSP for testing
the lossless compresstion algorithms with Canterbury Corpus.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
|
|
|
|
|
| |
Add a new recipe Calgary Corpus for Crystal Forest BSP
for testing the lossless compression algorithms.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|
|
Initial checkin for the new Crystal Forest BSP.
This BSP is based on Sandybridge CPU and Cave Creek Chipset.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
|