Closed Flamefire closed 2 years ago
Thanks.
A kernel version change to another 4.x kernel is not that easy. Quite a few of the blobs depend on the kernel version. Porting can be quite of a pain (but feel free to try :)
At least the BPF stuff is fully backported to 4.4. now. The only annoying this is lack of updates from kernel.org and CAF. Initially, i though the CIP guys ( https://www.cip-project.org/ ) wanted to take care of supporting 4.4 for another 10 years or so, but haven't looked into it.
Had a quick look, see here for example: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/tree/v4.4.302-cip70
Not sure if these are all backports or not, not understanding the naming scheme of their branches right now.
A kernel version change to another 4.x kernel is not that easy. Quite a few of the blobs depend on the kernel version. Porting can be quite of a pain (but feel free to try :)
I backported a few things to 4.9 (which CIP ports to 4.4) and Greg KH from the Linux kernel team told me to "just" switch to a newer version and that SONY would need to provide the sources of such blobs depending on the kernel.
At least the BPF stuff is fully backported to 4.4. now. The only annoying this is lack of updates from kernel.org and CAF. Initially, i though the CIP guys ( https://www.cip-project.org/ ) wanted to take care of supporting 4.4 for another 10 years or so, but haven't looked into it.
They are. I'm using it in my fork (17.1/18.1 branches). Basically this is the right branch to track: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/?h=linux-4.4.y-st
This is from the latest ASB: https://source.android.com/security/bulletin/2022-08-01#qualcomm-components
I also moved the debug print to the place where it belongs to not use a wrong beid.
BTW: What was the reason we stick to the 4.4 kernel and not upgrade to a newer one? Is that (easily) possible (e.g. by a merge)?