On Friday 13 March 2015 15:25:03 Darren Hart wrote: > On 2/26/15 11:26 PM, [email protected] wrote: > > From: sundararaja perumal <[email protected]> > > > > Intel's QuickAssist Technology is designed to optimize the use and > > deployment of algorithm accelerators in networking and security > > applications. > > As the complexity of networking and security applications continues to > > grow, systems need more and more computational resources for workloads, > > including cryptography, data compression, and pattern matching. > > Intel QuickAssist Technology is designed to optimize the use and > > deployment of algorithm accelerators in these kinds of applications. > > > > Intel QuickAssist Technology employs a hardware-assisted security engine > > for implementing major security functions in both wired and wireless > > applications. This hardware-assisted security engine works to reserve > > processor cycles for application processing, and that in turn not only > > relieves CPU burden but also improves overall system performance. > > > > Intel QuickAssist Technology, made integral to the Intel architecture, > > aims to address the demand for hardware appliances with built-in > > security processing and to obviate the need for 3rd party co-processors. > > > > The Intel QuickAssist Technology software consists of an QAT API > > that is implemented by a driver which in turn drives the > > Intel QuickAssist Accelerator hardware. > > The acceleration driver can run in either kernel space or in user space. > > When running in user space, the acceleration driver accesses the > > hardware directly from user space. > > This Patch enables the QAT core for both Highland forest and > > Crystal forest Platforms. > > > > The Top-levelpackage name is "QATmux". > > For sub-packages, name is one of the following: > > 1.QAT1.5. for use with Intel Communications Chipset 8900 to 8920 Series. > > 2.QAT1.6. for use with Intel Communications Chipset 8925 to 8955 Series. > > The QATmux can interface to both QAT1.5 and QAT1.6 to bring up DH89xxcc > > and DH895xcc devices. > > > > The machine specfic packages are listed below to enable QAT-core. > > QAT-core packages-split contains: > > PACKAGES += "${PN}-dh89xxcc" > > PACKAGES += "${PN}-dh895xcc" > > PACKAGES += "${PN}-app-dh89xxcc" > > PACKAGES += "${PN}-app-dh895xcc" > > PACKAGES += "${PN}-dbg-dh89xxcc" > > PACKAGES += "${PN}-dbg-dh895xcc > > -dbg has a specific meaning in yocto and impacts the QA checks and other > packaging routines. I believe these should properly be named: > > ${PN}-dh89xxcc-dbg
This is correct, although strictly speaking we try to keep one dbg package per recipe rather than splitting them out. I believe there are parts of the system that don't handle split dbg/dev packages properly, so if we do do this we should have a compelling reason to do it. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
