<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size: 12pt; color: rgb(0, 0, 0); font-family: Calibri,Arial,Helvetica,sans-serif,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols;" dir="ltr"> Hi Paolo / Oliver, Thank you for your email. <div>> On Wed, Feb 22, 2017 at 10:19:25AM +0100, Oliver Grawert wrote: > > > The AppArmor patches that we ported from the > > > http://kernel.ubuntu.com/git/ppisati/ubuntu-vivid.git/tree/arch/arm/c > > > onfigs/snappy?h=snappy_v3.10 > > > > > > are for the linux kernel 3.10. > > > > > > But the kernel that we are referring to is from 96boards - linux > > > kernel 4.4. > > > > this is definitely wrong, for 4.4 kernels you indeed need to use a 4.4 > > patch set, another thing for paolo to answer (i'm not even sure you > > need any patches at all on a 4.4 kernel, all bits might be in-tree > > already and just some config options might be enough)... > > Unfortunately he is not using our Xenial kernel, so he still needs some patches > for AA - here's a updated delta of patches on top of stable/linux-4.4.y: > > https://github.com/piso77/sample-kernels/commits/stable-4.4.y > <div>We downloaded the kernel source from: <a href="https://github.com/piso77/sample-kernels.git" class="OWAAutoLink">https://github.com/piso77/sample-kernels.git</a> Checked out the "stable-4.4.y" branch. The kernel version is 4.4.50 (Blurry Fish Butt). This kernel has all the latest patches that you have mentioned. So, we just ran the below commands to merge our defconfig with snappy, and distro.config: ARCH=arm64 ./scripts/kconfig/merge_config.sh arch/arm64/configs/defconfig kernel/configs/distro.config <div>cp .config arch/arm64/configs/defconfig ARCH=arm64 ./scripts/kconfig/merge_config.sh arch/arm64/configs/defconfig kernel/configs/snappy/*.config </div> cp .config arch/arm64/configs/defconfig Then checked in the code. Our snapcraft.yaml is at: <a href="http://pastebin.com/Na76t2ks" class="OWAAutoLink"> http://pastebin.com/Na76t2ks</a> <a href="http://pastebin.com/Na76t2ks" class="OWAAutoLink"></a>We are able to build the kernel snap successfully. Build logs at: <a href="http://pastebin.com/fphxyh46" class="OWAAutoLink">http://pastebin.com/fphxyh46</a> We are able to build the ubuntu os snap successfully by using the kernel snap from your kernel and gadget snap from the older source that we had got. But when we boot the kernel, we are getting stuck in kernel boot. It seems the kernel is not getting the initrd. The bootlogs are at: <a href="http://pastebin.com/eF2sCiyJ" class="OWAAutoLink">http://pastebin.com/eF2sCiyJ</a> Can you please let us know if we are missing something ?</div> Also, the dts files are different as compared to the 4.4.23 kernel source. So is there some work ongoing. Because the prebuilt binaries has already SMP booting enabled, while the current latest kernel version has only a primary core booting. > depending of the 4.4.x revision you are using, if you apply all the patches > above the "Linux 4.4.50" commit, you will get all you need. > </div> Are we missing any patches that you are referring to as we have pulled the latest kernel ? One more observation: We are using the below command to build the kernel using snapcraft.yaml: <div> sudo snapcraft --target-arch arm64 snap So, if we want to do a incremental build for the kernel, how can we achieve that ? Thanks, Sunny </div> <a href="http://pastebin.com/eF2sCiyJ" class="OWAAutoLink"></a> </div> ************************************************************************************************************************************************************* eInfochips Business Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. ************************************************************************************************************************************************************* </body> </html>