Related
I've seen at least 5 people now apply patches to the kernel source code to bring it up to a more recent version. To save the 6th and subsequent person from doing so, I pushed up a "clean" version of the stock (1.15, of course) kernel source code after merging in all linux mainline commits. FYI, to do so and preserve the history, I do:
git merge --strategy=ours v3.4.10
git merge v3.4.11
..
and resolve the conflicts as I go. There is a readme that explains (without having tested the procedure, so let me know if it needs to be tweaked) how to use to to patch an existing kernel source. This also serves as a good base if you want to start building a completely new kernel or if you want to compare your conflict resolutions to my conflict resolutions.
I plan to continue to update this with upstream patches as they are released as I will be using this to do my own merging of upstream commits.
The source is at http://github.com/crpalmer/dna-kernel-plus-upstream.
The branch "stock" contains the HTC released source code and also includes a commit that restores many of the comments that HTC stripped out of the source code when they released the 2.04 release. This should be much easier to merge with existing commits and make a more easily patched base of a kernel than what HTC released.
crpalmer said:
I've seen at least 5 people now apply patches to the kernel source code to bring it up to a more recent version. To save the 6th and subsequent person from doing so, I pushed up a "clean" version of the stock (1.15, of course) kernel source code after merging in all linux mainline commits. FYI, to do so and preserve the history, I do:
git merge --strategy=ours v3.4.10
git merge v3.4.11
..
and resolve the conflicts as I go. There is a readme that explains (without having tested the procedure, so let me know if it needs to be tweaked) how to use to to patch an existing kernel source. This also serves as a good base if you want to start building a completely new kernel or if you want to compare your conflict resolutions to my conflict resolutions.
I plan to continue to update this with upstream patches as they are released as I will be using this to do my own merging of upstream commits.
The source is at http://github.com/crpalmer/dna-kernel-plus-upstream.
Click to expand...
Click to collapse
this is awesome man thanks
Re: [Dev][Kernel][3.4.38] Stock source + Linux upstream commits
Sweet. Thanks man.
Sent from my HTC Droid DNA
Merged in the 2.04 source drop.
The branch "stock" contains the HTC released source code and also includes a commit that restores many of the comments that HTC stripped out of the source code when they released the 2.04 release. This should be much easier to merge with existing commits and make a more easily patched base of a kernel than what HTC released.
If you've already done your own merge (zarboz), you may want to try cherrypicking this commit:
https://github.com/crpalmer/dna-kernel-plus-upstream/commit/c81741a8337c2342d856ffeac0cc087452729290
Excellent Thanks for this, it's very handy
crpalmer said:
Merged in the 2.04 source drop.
The branch "stock" contains the HTC released source code and also includes a commit that restores many of the comments that HTC stripped out of the source code when they released the 2.04 release. This should be much easier to merge with existing commits and make a more easily patched base of a kernel than what HTC released.
If you've already done your own merge (zarboz), you may want to try cherrypicking this commit:
https://github.com/crpalmer/dna-kernel-plus-upstream/commit/c81741a8337c2342d856ffeac0cc087452729290
Click to expand...
Click to collapse
I looked through all my rej files and they were all comments I personally didn't care about lol
Thanks for the update though
hi Guys,
as some of u maybe know from the Samsung Galaxy S3 or OPO area i'm doing a "build-service" for non official boeffla kernel builds and as we recently also got a boeffla kernel
for the One Plus Two device (kudos to @Lord Boeffla!) i want to share with u my self made Linaro/Uber builds for that device in addition.
i'm gonna reduce redundancy and keep it shorter this time as about how this started and my primary intention can also be taken from the corresponding Samsung Thread
for people who asks themself: Linaro, Sabermod, Uber what? here some good info about it: https://docs.google.com/document/d/1C-ehLWl6XcStOmB30QHDA_DOdceXiGIyzXT_0eIg5nQ/edit (thx to @ViditM14 for providing the link!) and finally more infos about Uber Toolchains : https://plus.google.com/+ChetKener/posts/YzMJEkzPQgp and here: https://plus.google.com/communities...3/stream/ac70dec1-dad7-438d-baeb-f8d6644217fd
so without further ado let's go:
First of all the obligatorily Disclaimer:
As also written in the title please note these builds are UNOFFICIAL, are NOT SUPPORTED in any way by Lord Boeffla or myself and might be EVEN UNSTABLE! So take them as they are! As always flash them at your own risk and make a backup before flashing! (yeah take this advice seriously!)
About bugs: Before you report ANY issues with the linaro/uber builds provided here (doesn't matter which one!) FIRST TRY the non-linaro/uber official builds from HERE to see if they will be gone then. if they wont, you can go on and report your problems in the official boeffla kernel thread! I hope you understand that we have to treat and keep these builds here completely separate from official ones as they have in no terms something to do with each other! Not respecting this will force me to stop building further linaro/uber builds of boeffla kernel.
About benchmarks and comparisons between toolchains:
It's common known that linaro (maybe also uber?) builds might give us higher benchmark rates and that seems great for some people (in fact it's pointless per se in my opinion)
so please if you really must, post them ONLY here and NOT in official boeffla kernel thread, thanks!
Now some more precise informations about what's going on here:
what i did:
the images are always build with original sources from official boeffla kernel OPO repositories from HERE
with some not worth to mention minor changes to be able to build it on my build environment with non stock toolchains.
all images are compiled from special branches from this forked Boeffla Kernel repository
with a self compiled Linaro Toolchain 4.9.1-2014.07-1 (source: https://github.com/zanezam/ct-ng_linaro) + recent version of Uber Toolchain 4.9.4 (Credits to Team Uber for the pre-configured/-build toolchains)
all images are build with changes from different branches in following repository:
https://github.com/zanezam/boeffla-kernel-oos-oneplus2
Beside of some additional fixes from my side all changes are taken from repositories of @ak
so all credits to him, and thx again for the starting point!
before someone asks some last words about the used toolchain versions: i did a lot of testing before releasing these builds here
and the used Linaro / Uber versions are the maximum versions which can be used to make working builds with pure boeffla
kernel sources and without changing a lot of code in addition. So if u are able to biuld a kernel and still want to try higher versions i must state here that Linaro versions
above 4.9.1 and Uber verisions above 4.9.4 might produce a "messed up" image which at the end gives you a boot-looping or not booting device and that might even be dangerous, so be aware !!
if someone has a clue what exactly has to be done to use higher versions of the corresponding toolchains (with respecting the original kernel source of course) feel free to let us know,
it will be definitely appreciated!
what i will do:
build the source code with linaro/sabermod toolchain and (like Lord Boeffla usually does) provide a CWM image of recent boeffla kernel versions.
do a test for about 1 day with this builds and if they work without any big issues, add them here in the thread.
i will try to keep the linaro/uber toolchains as up-to-date as possible till the need of bigger code change will be reached.
not providing versions that are not released by Lord Boeffla yet.
not providing an image if it is not working - well of course not *g* but it will be marked as "canceled" then for info.
not change the source code to add/remove features or fix boeffla kernel related bugs.
not support the whole stuff here.
what i will maybe do (sooner or later):
provide ZZMoove Governor test builds if there are any new versions to test - more infos and discussions about ZZMoove Governor can be found HERE
maybe tune the build flags if some more linaro/sabermod/uber experienced dev comes up with "better" ones (feel free to post and let me know, toolchain specialists! *g*)
Downloads:
One Plus Two Oxygen OS 2.x.x
(*l491* linaro / *u494* uber)
One Plus Two Oxygen OS 3.x.x
(*l491* linaro / *u494* uber)
One Plus Two CM13.0
(*l491* linaro / *u494* uber)
One Plus Two CM14.1 / LineageOS 14.1
(*l491* linaro / *u494* uber)
Mirror on Androidfilehost for all devices (only latest kernel versions)
reserved
reserved too
Nice! Flashing now! Welcome
Sent from my ONE A2005 using Tapatalk 2
---------- Post added at 05:40 PM ---------- Previous post was at 05:15 PM ----------
@ZaneZam do you own our device or are you just optimizing the Lord's builds?
Sent from my ONE A2005 using Tapatalk 2
jmtjr278 said:
Nice! Flashing now! Welcome
Sent from my ONE A2005 using Tapatalk 2
---------- Post added at 05:40 PM ---------- Previous post was at 05:15 PM ----------
@ZaneZam do you own our device or are you just optimizing the Lord's builds?
Sent from my ONE A2005 using Tapatalk 2
Click to expand...
Click to collapse
yeah i got one lying in front of me (but not as a daily driver yet) so yes i'm also running these builds
i'm doing this only for devices i own, otherwise it wouldn't be possible to provide anything decent
btw guys don't be confused about the "COS" naming in the images that's just a typo and will be gone in next version, sry
If you don't mind me asking, what are you using as your dd? Opo still?
Sent from my ONE A2005 using Tapatalk 2
jmtjr278 said:
If you don't mind me asking, what are you using as your dd? Opo still?
Sent from my ONE A2005 using Tapatalk 2
Click to expand...
Click to collapse
yes
Man im so happy to have you here!
---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------
ZaneZam said:
yes
Click to expand...
Click to collapse
Lol me too until I have a good combo rom with your kernel
So glad to see you joining this party ZZ!
So glad to see more famous developers are coming forward to provide support. Please bring regular updates.
nirmalkurienmathews said:
So glad to see more famous developers are coming forward to provide support. Please bring regular updates.
Click to expand...
Click to collapse
will definitely do, even though for the used toolchain part it's harder than with other devices but time will tell
Love your work, will be flashing soon
Cheers !!
Whats the difference between U494 & 1491 ?
Just wanted to be sure before i flash, thanks !!
New Builds!
Funk Wizard said:
Whats the difference between U494 & 1491 ?
Just wanted to be sure before i flash, thanks !!
Click to expand...
Click to collapse
u494 = Build with Uber toolchain (gcc v4.9.4), l491 = Build with Linaro toolchain (gcc v4.9.1 ) apart from that optimization flags are the same atm.
u can flash any of these on top of offical builds or vice versa settings of boeffla app are preserved. which one is better or IF there are big differences isn't known yet
but let us know if u face any pros or cons with these builds here, thx !
and btw:
builds of...
Boeffla-kernel-1.0-beta2-OOS2xx-OnePlus2
uploaded!
Enjoy!
ZZ
Under Testing..
Thanks a lot @ZaneZam, You finally arrived officially
ZaneZam said:
u494 = Build with Uber toolchain (gcc v4.9.4), l491 = Build with Linaro toolchain (gcc v4.9.1 ) apart from that optimization flags are the same atm.
u can flash any of these on top of offical builds or vice versa settings of boeffla app are preserved. which one is better or IF there are big differences isn't known yet
but let us know if u face any pros or cons with these builds here, thx !
and btw:
builds of...
Boeffla-kernel-1.0-beta2-OOS2xx-OnePlus2
uploaded!
Enjoy!
ZZ
Click to expand...
Click to collapse
Thanks Zam for your explanation, running the beta2 for few hours now and it looks promising.
Cheers !!
Thanks! The really good kernel!
Thanks for your work.
I have one question for you...
Are you abel to build official kernel (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8994) with uber/linaro toolchain?
I have a lot of error when I try to build official kernel with uber toolchain
Thanks,
Flavio
Didn't try but as boeffla kernel uses this as base I can say : Only with v4.9.4 from uber and a self made Linaro 4.9.1. with uber 5.x or 6.x there are errors which I was able to fix (except one ice on latest 6.x but that's a bug in gcc which will be fixed in next toolchain version hopefully) but however the 5.x and 6.x images are not booting at the moment. this needs some special attention or some special knowledge which I don't have atm
Gesendet von meinem ONE A2003 mit Tapatalk
sorry for the stupid question, but what is the difference between this kernel and official boeffla kernel??
Now as kernel source is released, will MiPad get updated roms??
(Android M/N)
Link for the kernel source?!
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/mocha-kk-oss
The link to sources
our blobs are very very old
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Very Nice.!!! :fingers-crossed:
nathanchance said:
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
Click to expand...
Click to collapse
Thanks for everything Sir.
You really are techno-Jesus, here to teach the ways of kernel perfection. I love your work, dedication, and care for your kernel users. Flash4lyfe.
Yes, please flame me for being a fanboy. You can never show enough appreciation for our beloved xda developers (especially the ones that don't treat users like ****).
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
AndroidGX said:
Many thanks for your work and initiative @nathanchance :good: appreciated :highfive:
Currently giving a try to make a kernel version based from linux .116 of your op5 branch and looks like I have the following error :
Code:
fs/f2fs/f2fs.h:136:20: error: static declaration of 'inode_nohighmem' follows non-static declaration
Any idea ? I was thinking of a "KBUILD_CFLAGS" addition into Makefile (or something like that), but I'm probably wrong I guess.
FYI I'm using stock 4.9 android google toolchain
Click to expand...
Click to collapse
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
nathanchance said:
Wow I am so sorry about that, I must not have built 4.4.116 I removed all of the upstream f2fs code in my own kernel tree so I didn't encounter this error. I have pushed the fix that popped up in kernel/common, should be able to pull and build successfully now :good: :highfive:
Click to expand...
Click to collapse
No worries
Thanks, it works like a charm now (currently trying my kernel on .116), again good job :highfive:
Cheers'
4.4.117 has been merged in.
4.4.118 has been merged in (conflict notes).
4.4.119 and OOS 5.0.4 have been merged in.
4.4.120 has been merged in (conflict notes).
thanks for making this, trying to build lineage and I keep getting the following error:
Code:
drivers/bluetooth/btfm_slim.c:26:23: fatal error: btfm_slim.h: No such file or directory
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
Use an out folder.
mkdir out
make O=out mata_defconfig
make O=out -j$(nproc --all)
Click to expand...
Click to collapse
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
aeppacher said:
thanks for making this, trying to build lineage and I keep getting the following error:
Any ideas?
---------- Post added at 10:47 PM ---------- Previous post was at 10:20 PM ----------
lol, found one of your comments on another post that helped
new problem, the kernel compiles into an Image.gz, how would I go about getting a zImage for use in AnyKernel
Click to expand...
Click to collapse
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
nathanchance said:
That is the zImage (you'll actually want to use Image.gz-dtb), you can just add it to the AnyKernel2 zip as is, the backend handles that name.
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
It booted perfectly, thanks so much! I would use the thanks button but it doesn't seem to be working :/
4.4.121 has been merged in.
I will have a new tree based on the 8.1 sources out tonight.
Sent from my Google Pixel 2 XL using XDA Labs
I have added a new branch for the 8.1 beta source; I will continue to update both 8.0 and 8.1 until 8.1 goes stable.
https://github.com/android-linux-stable/op5/commits/oneplus/QC8998_O_8.1
4.4.122 has been merged in.
4.4.123 has been merged in.
http://en.miui.com/thread-4513744-1-1.html
Post to the link above and ask for the kernel source to be public.
THX!