Hi Rebecca,
As this will be changing the kernel version as well. This change brings in
the risk of further delay for the valleyland BSP with the meta-intel 1.6.1
release. How much validation have you done with this change?
As some components from SDK image are sensitive to the kernel version.
We have a new hardware crypto device driver currently out for RFC on the
linux-crypto mailing list and would like to back-port it to the Yocto Linux
kernels once it is committed upstream. What is the process for getting it into
the current dev kernel as well as linux-yocto-3.10 and
I have just removed two SMBUS patches from the feature branch as the 2 patches
have been pulled into standard/base. I have done a build test and sanity test
upon boot up. If you have concern, we can put this changes on hold and we can
wait until meta-intel 1.6.1 release settled down first. We
On 6/18/2014 4:24 PM, Allan, Bruce W wrote:
We have a new hardware crypto device driver currently out for RFC on
the linux-crypto mailing list and would like to back-port it to the
Yocto Linux kernels once it is committed upstream. What is the process
for getting it into the current dev
On 2014-06-18, 9:51 PM, Kamble, Nitin A wrote:
On 6/18/2014 4:24 PM, Allan, Bruce W wrote:
We have a new hardware crypto device driver currently out for RFC on
the linux-crypto mailing list and would like to back-port it to the
Yocto Linux kernels once it is committed upstream. What is the
On 2014-06-18, 8:29 PM, Chang, Rebecca Swee Fun wrote:
I have just removed two SMBUS patches from the feature branch as the 2 patches
have been pulled into standard/base. I have done a build test and sanity test
upon boot up. If you have concern, we can put this changes on hold and we can
