Related
Just noticed this over on Notion Ink's website...
Android 2.3 comes with Kernel version 2.6.35. The latest which NVidia Tegra works with is 2.6.36! http://android.git.kernel.org/?p=kernel/tegra.git;a=summary
Click to expand...
Click to collapse
Perhaps some one far smarter than me can make use of this info...
I don't think the stock tegra kernel has all the drivers necessary for the G Tablet. Because I think people have known about that repository, and as far as I know, nobody's built their own kernel that's worked with the G Tablet, but rather have been using kernels pre-built for the G Tablet or the ZPad.
This is why people keep talking about wanting the source from Viewsonic.
But if somebody wants to try doing a kernel build and seeing what does or doesn't work, more power to you!
This is actually only sort of related, but I noticed screenshots a few days ago of what was supposedly 2.3, but the about phone item show a 2.6.29 kernel version like 2.0 & 2.1 use, while 2.2 uses 2.6.32, and I knew that 2.3 was also getting a kernel update..
Oddly enough noone commented on that in the comment section on that site, and I just couldn't be bothered to create an acct to comment...
I've searched nvidia's git repo for our touchscreen drivers and they are not there. Therefore, trying to build from nvidia's git for the gtab won't do us any good until Viewsonic (malata, etc.) posts the kernel source.
this may sound silly. but can we somehow maybe get drivers from the touchscreen for the tegra? instead of looking for drivers from nvidia for the screen can we look for drivers from the screen maker for the tegra?
Bukem75 said:
Just noticed this over on Notion Ink's website...
Android 2.3 comes with Kernel version 2.6.35. The latest which NVidia Tegra works with is 2.6.36! http://android.git.kernel.org/?p=ker....git;a=summary
Perhaps some one far smarter than me can make use of this info...
Click to expand...
Click to collapse
Their NI Adam is not coming with Android 2.3, it comes with the scandal or it's hardly coming in at all: http://fineoils.blogspot.com
Now that we have the kernel source patch, I thought it would be good to summarise what's in it.
I've made a start here:
https://spreadsheets.google.com/ccc?key=tqj3aStfFS2K5PO83we84TQ&authkey=CI6h0aMD#gid=0
Because we don't have a full changelog, and it's a big patch, I thought it would be helpful to summarise what was changed in each file which brief comments. If you can help fill in the gaps for the modified files please post below.
Note that the patch appears to include a lot of cruft (multiple redundant backup copies of some files) I'd like to verify which files are redundant and produce a filtered, simplified patch. If you can confirm that the marked files are redundant that would be helpful.
I note that there are a few points where there is debug code and fixme comments in the patch. These may point to areas where things were never quite worked out (eg power management?). I don't have enough experience to look into this more deeply but just thought I'd mention it here.
Finally, the mmc driver has been brought in from outside the nv-tegra tree. It would be useful to generate a diff against the mainline tree to understand what (if anything) has changed there.
Happy Christmas!
I'm not very android dev savvy either...but they may have left the old drivers in there because old ROMs refer to them and they wanted to preserve the ability to go back to previous ROMs? -- that is...if the ROMs reference the kernel for drivers...not quite sure how that whole thing works...just a thought.
I've built a kernel from these sources, but unfortunately the bootloader throws a "magic value mismatch" error rather than booting the kernel. Has anybody else had any better luck?
EDIT: my bad, I replaced the boot.img with the raw zImage. I now have it booting my kernel, but it dies like this when starting Android:
I/SurfaceFlinger( 1072): SurfaceFlinger is starting
I/SurfaceFlinger( 1072): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/Zygote ( 1070): Process 1072 terminated by signal (11)
I/Zygote ( 1070): Exit zygote because system server (1072) has terminated
Any lines starting with - are deleted code.
NMCBR600 said:
Any lines starting with - are deleted code.
Click to expand...
Click to collapse
Yeah, in the patch itself, lines starting with + are added, and starting with - are deleted.
In the spreadsheet linked above, lines starting with + are files added, -files deleted, and !modified.
Actually the patch deletes no files, but /arch/microblaze/boot/dts/system.dts is overwritten with a new one. Anyone know exactly what that file does?
I started this because when I was reading the patch it seemed like a lot of new files were added and I wanted to work out where they came from, but it now looks like a lot of the added files are just backup copies the Malata dev has left in the tree (not a bad programming practice during development, but makes the patch a bit confusing to read).
Seems like the new files that are added (that aren't backups) are:
+ touch screen drivers in arch/arm/mach-tegra/odm_kit/platform/touch/{ak4183,at168}
+ driver for buttons in drivers/input/keyboard/so340010_kbd.c
+ drivers for gps control (power on/off), light sensor and accellerometer in drivers/input/misc/{gps_control.c,isl29023_ls.*,lis35de_accel.*}
+ drivers for batteries in drivers/power/smba10xx_battery and drivers/power/yoku_0563113
+ drivers for headphone and dock switches in drivers/switch/{switch_dock.c,switch_h2w.c} (header file in include/linux/switch_dock.h)
Also, mmc driver (presumably from mainline linux) is imported drivers/mmc
+ drivers for gps control (power on/off), light sensor and accellerometer in drivers/input/misc/{gps_control.c,isl29023_ls.*,lis35de_accel.*}
Sounds promising ..
Can someone explain to me perhaps if I'm missing something here- but what I am to understand from this post is that we finally got the source for the gtablet kernel? Would this incline to mean that we could compile the touchscreen and etc drivers onto a standard linux kernel and pop ubuntu or other such on the gtablet?
Or is 'patch' referring to just some small subset of the code missing the majority required to compile a gtablet kernel?
Any chance we might then be able to hack a fix into the accelerometer code to align the axis correctly?
rswindle said:
Can someone explain to me perhaps if I'm missing something here- but what I am to understand from this post is that we finally got the source for the gtablet kernel? Would this incline to mean that we could compile the touchscreen and etc drivers onto a standard linux kernel and pop ubuntu or other such on the gtablet?
Click to expand...
Click to collapse
One would have to recompile Ubuntu (or whatever distro) for ARM. Also, a finger friendly GUI would have to be added allowing the Capacitive screen to do its thing. Its very possible now with the kernel but no, you cannot use the iso downloaded from ubuntu.com.
rswindle said:
Can someone explain to me perhaps if I'm missing something here- but what I am to understand from this post is that we finally got the source for the gtablet kernel? Would this incline to mean that we could compile the touchscreen and etc drivers onto a standard linux kernel and pop ubuntu or other such on the gtablet?
Or is 'patch' referring to just some small subset of the code missing the majority required to compile a gtablet kernel?
Any chance we might then be able to hack a fix into the accelerometer code to align the axis correctly?
Click to expand...
Click to collapse
The drivers for the touchscreen, battery, and the accelerometer are all there in the kernel patch or the Nvidia tegra2 repo that it's patched again, yes. It's up on Viewsonic's website, in the support section.
Yes, you can merge them into an Ubuntu kernel if you want to. I'm sure somebody will do that in the next few weeks/months, it just hasn't happened yet since we just got the code dropped a few days ago.
There's some threads in NVidia's tegra2 dev forums on getting Ubuntu to work with a tegra 2 kernel. I posted the link earlier today if you're curious, look through my posts.
Great, so then the next question is, has anyone yet gotten a bootable compiled kernel from these yet?
Would be cool to get a stock android system compiled against a standard kernel for gtab.
Now I'm going to have to go rig up a linux thumb when I get home to start compiling the kernel with the patched sources and see what I can do. I so want to fix the damn accelerometer..
Best of all, my wife can play angry birds the entire time so she won't complain our HTPC is being used for my insanity..
Any suggestions what's a super lite fast distro to toss on a thumb quick that would quickly have me in position to git linux sources and compile this kernel? I don't keep up with the distros these days..
Yes
rswindle said:
Great, so then the next question is, has anyone yet gotten a bootable compiled kernel from these yet?
Would be cool to get a stock android system compiled against a standard kernel for gtab.
Now I'm going to have to go rig up a linux thumb when I get home to start compiling the kernel with the patched sources and see what I can do. I so want to fix the damn accelerometer..
Best of all, my wife can play angry birds the entire time so she won't complain our HTPC is being used for my insanity..
Any suggestions what's a super lite fast distro to toss on a thumb quick that would quickly have me in position to git linux sources and compile this kernel? I don't keep up with the distros these days..
Click to expand...
Click to collapse
I believe at least a half dozen of us have now built and deployed our own kernels. I've started cherry-picking Nvidia fixes beyond the baseline looking for something to fix the slowdown problem. Trying the latest variation now.
As for the accelerometer, I don't play any games where that is an issue, so I don't know if this resolves the problems, but there is a 1 line patch beyond our baseline in the Nividia tree which switches the X axis. Maybe this is the issue?
The patch description is:
X direction needs to be reversed to correct orientation in portrait
mode for Whistler.
Bug 678250
and the code diff is here:
http://nv-tegra.nvidia.com/gitweb/?...ff;h=6d57f00bb8276e0392dfa199017fc70fcea7d60b
I have applied this in my current kernel, but I've never seen the bug and can't tell you if it makes a difference.
[email protected] said:
I believe at least a half dozen of us have now built and deployed our own kernels. I've started cherry-picking Nvidia fixes beyond the baseline looking for something to fix the slowdown problem. Trying the latest variation now.
As for the accelerometer, I don't play any games where that is an issue, so I don't know if this resolves the problems, but there is a 1 line patch beyond our baseline in the Nividia tree which switches the X axis. Maybe this is the issue?
The patch description is:
X direction needs to be reversed to correct orientation in portrait
mode for Whistler.
Bug 678250
and the code diff is here:
http://nv-tegra.nvidia.com/gitweb/?...ff;h=6d57f00bb8276e0392dfa199017fc70fcea7d60b
I have applied this in my current kernel, but I've never seen the bug and can't tell you if it makes a difference.
Click to expand...
Click to collapse
mdwalker, I've likewise built my own kernel and have been running it too. I likewise have been trying to isolate and fix the slowdown problem. I likewise haven't succeeded yet.
There are a bunch of patches in the Nvidia tree that relate to suspend-resume issues, which I'm sure you've noticed. Let me know if you zero in on anything.
question.. I noticed all the developers are from Nvidia, I would think they would be Viewsonic developers... and if not the case are these bugs were not caught a while ago?
Viewsonic doesn't make this
stanglx said:
question.. I noticed all the developers are from Nvidia, I would think they would be Viewsonic developers... and if not the case are these bugs were not caught a while ago?
Click to expand...
Click to collapse
Viewsonic doesn't make our tablet, it's made by a Chinese company called Malata based on a standard Nvidia design. Viewsonic just resells it in the US.
There are actually a number of "rebadged" variations of this tablet, with more appearing almost every day.
Absolutely
rcgabriel said:
mdwalker, I've likewise built my own kernel and have been running it too. I likewise have been trying to isolate and fix the slowdown problem. I likewise haven't succeeded yet.
There are a bunch of patches in the Nvidia tree that relate to suspend-resume issues, which I'm sure you've noticed. Let me know if you zero in on anything.
Click to expand...
Click to collapse
Yes, I've certainly noticed the suspend/resume functionality looks to be a frequent source of "fixes". There are lots of patches which sound promising. Hopefully one (or more, gah!) will do the trick without having to hack up the cpu power management itself.
Likewise if you (or pershoot, or ... whomever else is tinkering) finds the right combination, please let us know!
Understand that... The point I am making is why is there so much Nvidia development going on for a version of the Kernel that is considered stable?
[email protected] said:
Viewsonic doesn't make our tablet, it's made by a Chinese company called Malata based on a standard Nvidia design. Viewsonic just resells it in the US.
There are actually a number of "rebadged" variations of this tablet, with more appearing almost every day.
Click to expand...
Click to collapse
rswindle said:
Now I'm going to have to go rig up a linux thumb when I get home to start compiling the kernel with the patched sources and see what I can do. I so want to fix the damn accelerometer..
Click to expand...
Click to collapse
Don't waste your time on the accelerometer, as the problem is with the app devs, not our device.
A nice explanation is here: http://android-developers.blogspot.com/2010/09/one-screen-turn-deserves-another.html
iptables owner module
One of the critical features I am looking for is a kernel built with support for iptables, and specifically the "owner" module.
This is used by apps such as Droidwall and my own app, Orbot, which is the port of Tor to Android. I worked with Cyanogen on this issue previously and am hoping to get this into all of the ROMs for the GTablet as well.
Thanks!
stanglx said:
Understand that... The point I am making is why is there so much Nvidia development going on for a version of the Kernel that is considered stable?
Click to expand...
Click to collapse
Why are you considering it's stable? Afaik there are very few products running the NVIDIA kernel at this stage -- the base hardware target is "harmony", which is actually one of NVIDIA's development boards.
G Tablet is one of the first Tegra 2 based products and we are about to see a whole raft of them over the next 6 months. Starting with Gingerbread tablets and then going to Honeycomb. If you check the logs you'll see that stuff from nv-tegra repo is being merged into the AOSP repo pretty regularly at the moment. Presumably, preparing for the Motorola Tegra 2 tablet. I imagine NVIDIA devs are quite busy on that.
I think a bigger question is why the very different codes at kernel.org and Navdia's own repository? In some cases commits are pulled in from each other, but clearly they are on different paths. Motorola seems to be pushing commits to kernel.org.
s_frit said:
Why are you considering it's stable? Afaik there are very few products running the NVIDIA kernel at this stage -- the base hardware target is "harmony", which is actually one of NVIDIA's development boards.
G Tablet is one of the first Tegra 2 based products and we are about to see a whole raft of them over the next 6 months. Starting with Gingerbread tablets and then going to Honeycomb. If you check the logs you'll see that stuff from nv-tegra repo is being merged into the AOSP repo pretty regularly at the moment. Presumably, preparing for the Motorola Tegra 2 tablet. I imagine NVIDIA devs are quite busy on that.
Click to expand...
Click to collapse
Being released by NVIDIA this afternoon is the Tegra 12 Alpha 1 Linux release. This is a Linux software release intended for developers using NVIDIA's Tegra 2 platform.
The NVIDIA Tegra Linux 12 Alpha 1 release is based on the Linux 2.6.38 kernel and is derived from Ubuntu. Graphics standards supported by this Tegra-ified Ubuntu release include OpenGL ES 1.1/2.0, EGL 1.3, OpenMAX IL 1.1, and RandR 1.3.
For those interested in Linux for Tegra 12 Alpha 1, the relevant links are available from this forum thread.
Found by edgan
O.... so this replaced webtop? (or might/will?)
Edit: We don't have the Tegra 250 chip, I think we have have the Tegra 200 chip... the driver package is for 250.
Mgamerz said:
O.... so this replaced webtop? (or might/will?)
Edit: We don't have the Tegra 250 chip, I think we have have the Tegra 200 chip... the driver package is for 250.
Click to expand...
Click to collapse
The changelog says it supports the 200 series.
Nice but this belongs in the General forum.
If you didn't create it, it doesn't belong in development. It's a nice sticky that is on other devices' development forum and i think it applies here as well.
franciscojavierleon said:
Nice but this belongs in the General forum.
If you didn't create it, it doesn't belong in development. It's a nice sticky that is on other devices' development forum and i think it applies here as well.
Click to expand...
Click to collapse
You are probably right, I got overly excited and posted it here, please move to it the appropriate forum.
Cheers
I also think this belongs in general but here is a actual link to the official site @ nvidia
http://developer.nvidia.com/content/linux-tegra-release-12-alpha-1-released
txtsd said:
The changelog says it supports the 200 series.
Click to expand...
Click to collapse
But it looks like the Alpha Release only supports Tegra 250 "Harmony".
Taking directly from the Release Notes,
Code:
Note: This alpha release of Tegra Linux Driver Package (L4T.ER1 ) is a
release for Tegra 250 “Harmony” only. The information in these release
notes is preliminary
According to pdadb.net Atrix has Tegra 2 250 chip, also wikipedia says it has Tegra 250 AP20H (H stands for Harmony?)
[email protected] said:
According to pdadb.net Atrix has Tegra 2 250 chip, also wikipedia says it has Tegra 250 AP20H (H stands for Harmony?)
Click to expand...
Click to collapse
That is correct. There is no Tegra 200.
The Tegra 250 AP20H is the chip used in phones, Tegra 250 T20 is used in tablets. As far as I can tell, the biggest difference between the two SoCs is that the Geforce ULP GPU is clocked higher on the tablets (333mhz vs 300).
So this could be huge for WebTop?
Cheers
pederb said:
So this could be huge for WebTop?
Click to expand...
Click to collapse
Possibly... but to be honest, I'm not willing to give up Flash to go up to 11.04, let alone things like the Android-In-Window functionality. Updated versions of those are a lot harder to get. It might be able to get an updated Flash if we could find a Linux-based device out there that we could hack, but the others...? Good luck.
I'll be trying an upgrade to Ubuntu 10.04 at some later point in time, but I can't make any promises that it will succeed.
Sogarth said:
Possibly... but to be honest, I'm not willing to give up Flash to go up to 11.04, let alone things like the Android-In-Window functionality. Updated versions of those are a lot harder to get. It might be able to get an updated Flash if we could find a Linux-based device out there that we could hack, but the others...? Good luck.
I'll be trying an upgrade to Ubuntu 10.04 at some later point in time, but I can't make any promises that it will succeed.
Click to expand...
Click to collapse
So flash is not available in 11.04?
pederb said:
So flash is not available in 11.04?
Click to expand...
Click to collapse
NVIDIA might provide one to some of its OEM/ODM customers, but I don't think they publicly distribute Flash for public consumption. I expect it'll be the same in this case - if we could somehow get our hands on a leak of Flash for Ubuntu 10.10 or 11.04, we might be able to get something working, but otherwise, we're pretty much out of luck.
Depending on what kind of performance gains there are, this could be awesome. Although you wouldn't directly replace it, you'd be better off making a custom "distro" for the atrix using bits and pieces from webtop and combining them with the nvidia build.
Does anyone know exactly how the webtop environment boots? Important thing being the kernel. If it runs similar to a chroot you'd need a custom kernel as well.
Look up tegra on wikipedia we have 200 it says.
Sent from my Motorola Atrix 4G on the network with the most backhaul, whatever that is. This post might have errors as I hate touchscreen keyboards.
http://crap.muromec.org.ua/ac100/debian/2011-04-18/
http://markit.dyndns.org/ac100/
http://crap.muromec.org.ua/ac100/
http://paulfedora.wordpress.com/
http://ac100.163.ru/firmware/ubuntu/rootfs_11_04.tar.gz
theirs no massive difference between 200 and 250 as far as i know
hobbit19 said:
http://crap.muromec.org.ua/ac100/debian/2011-04-18/
http://markit.dyndns.org/ac100/
http://crap.muromec.org.ua/ac100/
http://paulfedora.wordpress.com/
http://ac100.163.ru/firmware/ubuntu/rootfs_11_04.tar.gz
Click to expand...
Click to collapse
What is all this?
Debian arm. Nvidia is optimizing for tegra (gpu driver included)... not just arm
Sent from my Motorola Atrix 4G on the network with the most backhaul, whatever that is. This post might have errors as I hate touchscreen keyboards.
DJ_Steve said:
theirs no massive difference between 200 and 250 as far as i know
Click to expand...
Click to collapse
There's no such thing as a Tegra 200 chip! Whenever it is referred to that way it is the because it's part of the 200 SERIES. Each being near identical with different clock speeds and possible some specific optimisations for the 3D models.
The Atrix has a Tegra 250 AP20H.
Hi guys!
First it's many months i don't come here on xda.
Second i haven't this device
...but i playing with this SoC from 2 months in a developers board (Odroid-XU-E).As you,i can go at 1.8 Ghz with A15 and 640 Mhz max with gpu when i build kernels for it..No luck until now in enabling 8 cores...also if for you is a bit useless,being the SoC in a phone on battery(where my board instead is AC powered!)but i know there were a lot of drama about it months ago about the CCI-400 bug
...and something is moving.look here those diff\patches
https://lkml.org/lkml/2013/10/1/264
https://lkml.org/lkml/2013/10/1/259
Thanks buddy. but i think samsung unofficially announced about not to support all 8 cores functional At one time.
Also what abiut heating and Boooom problem? I means, It may blast our mobile if not supported fully?
Edit: Seen that samsung official working on it.
A Suggestion: Change the thread name to True octa core.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Any pros to enlighten me what this actually means? Will this patch actually work?
Does it utilize the CCI400(which was believed to be broken) or other approach?
Sent from my GT-I9500 using xda app-developers app
sert00 said:
Hi guys!
First it's many months i don't come here on xda.
Second i haven't this device
...but i playing with this SoC from 2 months in a developers board (Odroid-XU-E).As you,i can go at 1.8 Ghz with A15 and 640 Mhz max with gpu when i build kernels for it..No luck until now in enabling 8 cores...also if for you is a bit useless,being the SoC in a phone on battery(where my board instead is AC powered!)but i know there were a lot of drama about it months ago about the CCI-400 bug
...and something is moving.look here those diff\patches
https://lkml.org/lkml/2013/10/1/264
https://lkml.org/lkml/2013/10/1/259
Click to expand...
Click to collapse
a word from @AndreiLux to make things clear..
thanks !
Will this patch actually work?
Click to expand...
Click to collapse
For us, basically no. These patches are for device-tree based kernels which our platform specific one isn't.
For the ODROID-XU / eventual theoretical DT based i9500 kernel it might be a possibility.
I see there's some non-standard alterations to the CCI driver related to the coherency ports, but they didn't even answer in the mailing list as to why they are there.
gdonanthony said:
a word from @AndreiLux to make things clear..
thanks !
Click to expand...
Click to collapse
i m also waiting for him. Posted the link in Previous thread of @AndreiLux buddy.
Sent from my GT-I9500 using XDA Premium 4 mobile app
AndreiLux said:
For us, basically no. These patches are for device-tree based kernels which is not part of ours.
For the ODROID-XU / eventual theoretical DT based i9500 kernel it might be a possibility.
I see there's some non-standard alterations to the CCI driver related to the coherency ports, but they didn't even answer in the mailing list as to why they are there.
Click to expand...
Click to collapse
@sert00 so here is the answer ... damn so sad about this things going on... and im hoping somethings will get better soon
thanks AndreiLux
AndreiLux said:
For us, basically no. These patches are for device-tree based kernels which our platform specific one isn't.
For the ODROID-XU / eventual theoretical DT based i9500 kernel it might be a possibility.
I see there's some non-standard alterations to the CCI driver related to the coherency ports, but they didn't even answer in the mailing list as to why they are there.
Click to expand...
Click to collapse
Does that mean it's a hardware level possibility, and just need to be implemented by clever brains?
They mentioned it was tested on 5410 dev board, dunno what that actually means..
Also regarding DT kernel, if I'm not wrong Linux is now forcing devs to switch to DT? So do you foresee any future for i9500 to actually have a DT kernel?
Forgive me if I was talking nonsense, I'm quite noob.
Sent from my GT-I9500 using xda app-developers app
lch920619x said:
Does that mean it's a hardware level possibility, and just need to be implemented by clever brains?
They mentioned it was tested on 5410 dev board, dunno what that actually means..
Also regarding DT kernel, if I'm not wrong Linux is now forcing devs to switch to DT? So do you foresee any future for i9500 to actually have a DT kernel?
Forgive me if I was talking nonsense, I'm quite noob.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
I doubt Samsung will ever switch the current generation to a DT model much like they never update older phone's kernels, but backport the needed bits. They're talking about the SMDK board which are LSI internal development boards. It is a STUPID amount of effort to switch over to a DT kernel, any hope is that some third-party gets some kind of update on the matter and be able to pull from that. Even the XU has only some half-hearted DT support and they work mostly on the platform kernel which is similar to ours.
Alternatively I could just pull the relevant MCPM backend and that new EDCS from the patch and try to get hack something together. But I would want to at least those patches to be actually accepted into mainline and have the 5410 supported there before one begins on an adventure into unknown territory.
AndreiLux said:
I doubt Samsung will ever switch the current generation to a DT model much like they never update older phone's kernels, but backport the needed bits. They're talking about the SMDK board which are LSI internal development boards. It is a STUPID amount of effort to switch over to a DT kernel, any hope is that some third-party gets some kind of update on the matter and be able to pull from that. Even the XU has only some half-hearted DT support and they work mostly on the platform kernel which is similar to ours.
Alternatively I could just pull the relevant MCPM backend and that new EDCS from the patch and try to get hack something together. But I would want to at least those patches to be actually accepted into mainline and have the 5410 supported there before one begins on an adventure into unknown territory.
Click to expand...
Click to collapse
I have to admit i got some difficulties understanding part of your post.
However I think I grasp the main idea and I'm looking forward to seeing how things will work once you try to implement the patch. Thanks for your effort.
BTW I'm using Chinese C version ROM(ZCUCMH1 to be specific), if I flash perseus ontop of my ROM, camera will refuse to open and report camera failure.
Not asking you to solve it but just curious if you can tell me what will possibily cause this?
Also if you have time can you point out what exactly is stopping us from having a fully functional AOSP build?
We got full kernel source code due to GPL, don't we?
And in another post you said it's nothing to do with documentation.
So what is it?
Sent from my GT-I9500 using xda app-developers app
thanks for the answer andreilux!i posted it only as a info.also on odroid board will be ready only when mainlined on 3.13 kernel,as sad by a linux developer,and there's tons of works to do to others stuffs to works!
Call me crazy but the best kernel for the nexus 6 is coming to the nexus 9, a device I don't have
Zen kernel is pretty sane and doesn't have changes like SuperMegaIOBlastFrequency5Million, but somehow it manages a bigger improvement than all those changes put together primarily through better CPU scheduling for the light-numa workloads of our mobile devices (in other words, BFS)
I have a BFS port from v461 (minus SMT nice )for 3.10 android/msm along with most of Alfred Chen's -gc branch includes as well.
Anyway, the effects are noticeable in the nexus 6 (no more google now launcher lag, no more big list lag, no more 3 second clear all recent delay, better power consumption through better frequency scaling by design of sticky tasks)
I think it will be just as good on the nexus 9, however I don't have one of these devices in my possession so I'm not gonna ask for people to buy me one instead I'm just going to ask for testers.
I'd like to see the effects of BFS on arm64 and I'm sure everybody else would like to see the benefits -zen kernel brings.
PM me if you would like a weekend build. I need at least 3 but the more the merrier.
Zen kernel for nexus 6
Thanks,
B
Also if you ask for a build tell me what ROM and existing kernel you are on if applicable.
Will you be getting a N9 in the future?
Sent From Capsule Corp.
Ace42 said:
Will you be getting a N9 in the future?
Sent From Capsule Corp.
Click to expand...
Click to collapse
Probably not, I graduate next month and plan on expanding my open source endeavors then but I'd like to support the nexus devices + 1 or 2 other flag ships with zen at all times.
People are happy over at N6, they were happy back on gnex and evo 4g I'm sure they will like nexus 9 version too
The custom kernel landscape has changed since the old days because there's less problems with new devices, but zen still finds a way
I'm really looking to change issues as I see them here. I don't want to bolster big names, give me money, this project is mine, etc. I want to bolster the community effort in a way that aids in learning, growth , etc. Zen is all about real kernel improvements. in time there is an app I've had on the shelf for 3 years with a brilliant framework among other things that I want to GPL-ize and release.
bbedward said:
Probably not, I graduate next month and plan on expanding my open source endeavors then but I'd like to support the nexus devices + 1 or 2 other flag ships with zen at all times.
People are happy over at N6, they were happy back on gnex and evo 4g I'm sure they will like nexus 9 version too
The custom kernel landscape has changed since the old days because there's less problems with new devices, but zen still finds a way
I'm really looking to change issues as I see them here. I don't want to bolster big names, give me money, this project is mine, etc. I want to bolster the community effort in a way that aids in learning, growth , etc. Zen is all about real kernel improvements. in time there is an app I've had on the shelf for 3 years with a brilliant framework among other things that I want to GPL-ize and release.
Click to expand...
Click to collapse
At some point in time years ago I was a know nothing, figure out how to apply a patch, compile a kernel amateur. But through a great Linux, gentoo, arch , etc . community I have now become a proficient programmer, graduating with computer science + engineering degree in a few weeks.
the XDA community hasn't been about helping people learn or grow in any form. Its become a pit of protecting private property and don't take my work, don't ask dumb questions, just give up. I want to see more community efforts rather than private all mine type of stuff.
I've always wanted to develop a ROM or kernel, but the steps to just get Linux on my laptop is too much let alone driver support. If there was a simple way to use just windows 8 I would like to contribute to the N9 community.
Also I commend you for your studies, neither of those fields are easy from what I've heard. :good:
bbedward said:
At some point in time years ago I was a know nothing, figure out how to apply a patch, compile a kernel amateur. But through a great Linux, gentoo, arch , etc . community I have now become a proficient programmer, graduating with computer science + engineering degree in a few weeks.
the XDA community hasn't been about helping people learn or grow in any form. Its become a pit of protecting private property and don't take my work, don't ask dumb questions, just give up. I want to see more community efforts rather than private all mine type of stuff.
Click to expand...
Click to collapse
I was like you a know nothing about kernels
I started kernel development knowing nothing
I still don't know much but, I'm learning slowly
Im vary interested in the source code
Also to test
Ace42 said:
I've always wanted to develop a ROM or kernel, but the steps to just get Linux on my laptop is too much let alone driver support. If there was a simple way to use just windows 8 I would like to contribute to the N9 community.
Also I commend you for your studies, neither of those fields are easy from what I've heard. :good:
Click to expand...
Click to collapse
Thanks, many linux distributions nowadays make it incredibly easy to get started though I'd venture to say most of them will work out of the box with your hardware.
USBhost said:
I was like you a know nothing about kernels
I started kernel development knowing nothing
I still don't know much but, I'm learning slowly
Im vary interested in the source code
Also to test
Click to expand...
Click to collapse
Probably will have a test Friday, just going to use AnyKernel2 for the N9 probably (only replace fstab with f2fs support and no force encryption).
The N6 tree is here:
https://github.com/bbedward/ZenKernel_Shamu
The BFS branch is here (I split everything into individual branches on Zen):
https://github.com/bbedward/ZenKernel_Shamu/commits/sched_upstream_bfs_gc
Some of the stuff from my N6 kernel is a drop in for the N9 since they are both 3.10 based.
https://www.dropbox.com/s/uekphwlxvm2pya9/v3.10-zen0_anykernel_N9.zip?dl=0
Please make sure you have a backup plan if it doesn't work
It has almost identical to Zen-nexus 6 stuff:
- My sched_upstream_bfs_gc branch pretty much identical to the N6 kernel branch
- Not identical to the N6 branch because nvidia has a bunch of nonsense sched stat stuff I added into BFS also
- Fiops/BFQ in addition to the default stuff
- ext4 from v3.10.y stable
- newest f2fs
- usb fast charge support
- 2A charging
- fsync toggle
- upstream MM stuff from v3.10.y
- Several race condition fixes, memory leak fixes from upstream
- flar2 wake gesture support
- overclock support whatever elementalX has up to 2.5GHz
- USB fast charging
No idea if it works, please have a backup ready.
There's lots of compile warnings in the tegra kernel and I had to build myself an aarch64 compiler because I didn't have one.
bbedward said:
https://www.dropbox.com/s/uekphwlxvm2pya9/v3.10-zen0_anykernel_N9.zip?dl=0
Please make sure you have a backup plan if it doesn't work
It has almost identical to Zen-nexus 6 stuff:
- My sched_upstream_bfs_gc branch pretty much identical to the N6 kernel branch
- Not identical to the N6 branch because nvidia has a bunch of nonsense sched stat stuff I added into BFS also
- Fiops/BFQ in addition to the default stuff
- ext4 from v3.10.y stable
- newest f2fs
- usb fast charge support
- 2A charging
- fsync toggle
- upstream MM stuff from v3.10.y
- Several race condition fixes, memory leak fixes from upstream
- flar2 wake gesture support
- overclock support whatever elementalX has up to 2.5GHz
- USB fast charging
No idea if it works, please have a backup ready.
There's lots of compile warnings in the tegra kernel and I had to build myself an aarch64 compiler because I didn't have one.
Click to expand...
Click to collapse
Will test tomorrow
How did you update f2fs?
USBhost said:
Will test tomorrow
How did you update f2fs?
Click to expand...
Click to collapse
I will push the source up once I can later tonight. It's quite hefty so it will take awhile to push up the first time
The way I did everything is almost the exact same as the N6 kernel. Some nvidia garbage had to be implemented into BFS but that's it. And the device specifics like OC, 2A charging, etc.
https://github.com/bbedward/ZenKernel_Shamu/commits/f2fs_upstream
everything is exactly the same except the first f2fs commit "Sync with kernel/f2fs.git linux-3.10 branch"
There I basically just delete everything in fs/f2fs. copy/paste fs/f2fs from that branch, copy include/linux/f2fs* include/trace/events/f2fs (maybe? I forget where all the headers are exactly) and also update the Documentation/filesystem/f2fs.txt
The only reason I do that is because the f2fs/linux-3.10 branch is oddly based on linux-4.0. So simply merging or cherry picking won't work too well, and things like the msm and tegra kernel have different versions of f2fs already. So i just clear it all out and sync with that.
After that I pulled in all the newer commits from the f2fs/dev branch.
bbedward said:
I will push the source up once I can later tonight. It's quite hefty so it will take awhile to push up the first time
The way I did everything is almost the exact same as the N6 kernel. Some nvidia garbage had to be implemented into BFS but that's it. And the device specifics like OC, 2A charging, etc.
https://github.com/bbedward/ZenKernel_Shamu/commits/f2fs_upstream
everything is exactly the same except the first f2fs commit "Sync with kernel/f2fs.git linux-3.10 branch"
There I basically just delete everything in fs/f2fs. copy/paste fs/f2fs from that branch, copy include/linux/f2fs* include/trace/events/f2fs (maybe? I forget where all the headers are exactly) and also update the Documentation/filesystem/f2fs.txt
The only reason I do that is because the f2fs/linux-3.10 branch is oddly based on linux-4.0. So simply merging or cherry picking won't work too well, and things like the msm and tegra kernel have different versions of f2fs already. So i just clear it all out and sync with that.
After that I pulled in all the newer commits from the f2fs/dev branch.
Click to expand...
Click to collapse
O so thats how you did it
I was scratching my head with all the problems of cherry-picking I was having lol
Source is up:
https://github.com/bbedward/ZenKernel_Flounder
The real glory lives here:
https://github.com/bbedward/ZenKernel_Flounder/commits/sched_upstream_bfs_gc
bbedward said:
Source is up:
https://github.com/bbedward/ZenKernel_Flounder
The real glory lives here:
https://github.com/bbedward/ZenKernel_Flounder/commits/sched_upstream_bfs_gc
Click to expand...
Click to collapse
Thanks man
bbedward said:
https://www.dropbox.com/s/uekphwlxvm2pya9/v3.10-zen0_anykernel_N9.zip?dl=0
Please make sure you have a backup plan if it doesn't work
Click to expand...
Click to collapse
Could you provide a boot.img, to be used as in
Code:
fastboot boot boot.img
I tried with the zImage but that did not boot at all and I don't dare to flash it - yet
taronas said:
Could you provide a boot.img, to be used as in
Code:
fastboot boot boot.img
I tried with the zImage but that did not boot at all and I don't dare to flash it - yet
Click to expand...
Click to collapse
Did you flash it through recovery? This is where it needs to be flashed.
I plan on only providing AnyKernel version for the N9 though, so it requires existing ramdisk.
Somebody has to be willing to try this for me. All you have to do dirty flash your ROM or flash another kernel if it doesn't work.
bbedward said:
Somebody has to be willing to try this for me. All you have to do dirty flash your ROM or flash another kernel if it doesn't work.
Click to expand...
Click to collapse
Will do in a few hours
Ps I tryed what you did with f2fs
it built but data did not mount
I was encrypted also
Didn't boot for me. Tried on a 32gig encrypted n9, running cm12.1, wifi
dictionary said:
Didn't boot for me. Tried on a 32gig encrypted n9, running cm12.1, wifi
Click to expand...
Click to collapse
Maybe because CM12.1 is 5.1 based? This is all based on stock kernel.
I will look to see if there's compatibility issues.