yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
His source isn't outdated , all of superram is there or in the OP , its just not laid out in one branch . I'm pretty sure I know somewhat to do but I couldn't say it would be exactly like his kernel . I know all the commits and changes from the changelog in the OP , I've just never applied them to one single kernel , I like the kernel debugging tools/ logs and other things SR got rid of to go super light weight .
[Samsung Galaxy Nexus] pianistaPL:
It would be nice to see "your Mpokang" :) Just try, if you want and have time :)
[Samsung Galaxy Nexus] bsmitty83:
Lol , I just might , cuz I'm kinda interested too :sly:

Right now I'm building dirtyV with graphite and link time optimization , I'm curious to see the difference .

As for the 3.4 I'm still mulling how best to tackle it . with that project I need weekend time to do
[Samsung Galaxy Nexus] Nephilim:
I would be more than willing to test a Smitty SuperRam if you would take all of the ram freeing script and other mods Mpokwths added to his kernel and build an up to date version, after we got that working smooth I would also test a linaro optimized version of it.

It's your call but I would very much enjoy testing and helping perfect the ultimate settings for something like that! ;)

If you are interested feel free to hit me up in a PM here or over on G+ either on my profile or my Community. :good:
[Samsung Galaxy Nexus] Hetalk:
Count me in as well. Always ready to test stuff. :good:
[Samsung Galaxy Nexus] Nephilim:
What's up Hetalk! How you been? You should Join my new G+ Community, the links in my sig. Anarkia and MBQ_ already are members! It's like having the AK Thread but for everyone and everything!
[Samsung Galaxy Nexus] Hetalk:
Doing good buddy. Took a break from flashing/xda for a few months to attend to some other important stuff.

Came back to KK and new kernels and developers. Good to see people keeping this phone alive.:good:

BTW, just asked to join your community. :)
[Samsung Galaxy Nexus] bsmitty83:
I got you . i m working on a superram version linaro , couldn't get it to boot so I think its the config but as soon as it boots I'll post it .
[Samsung Galaxy Nexus] Nephilim:
Awesome, I can't wait man!!!! Super Stoked! :good:
[Samsung Galaxy Nexus] randommmm:
Please keep on man..... Somehow, this topic has me recall a famous line.... " if you build it, he will come " from the movie Field of Dreams. If you build it, we will try
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] A very good reference device that could be used to help bring up the tuna is the OMAP4 BlazeTablet2 bookmark the below gits ;)

https://github.com/rbilovol/device-ti-blaze_tablet

https://github.com/rbilovol/eurasia_km

https://github.com/rbilovol/kernel

ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support · 7c8f92c · rbilovol/kernel · GitHub - http://goo.gl/YcyD4x

ARM: DTS: OMAP4: Add OMAP4 Blaze Tablet support

The OMAP4 Blaze Tablet is TI OMAP4 processor-based

development platform in a tablet formfactor.

The platform contains many of the features found in

present-day handsets (such as audio, video, wireless

functions and user interfaces) and in addition

contains features for software development and test.

This patch adds initial support for the OMAP4 Blaze

Tablet development platform. Additional functionality

depends on different drivers and code modifications that

are not upstreamed yet or do not support DT yet, so will

be added later.

blaze_tablet: Switch to upstreamed OMAP4 Blaze Tablet DT machine name. · bda11ee · rbilovol/device-ti-blaze_tablet · GitHub - http://goo.gl/v3A03p

init: add support for DT

This patch changes default behavior when looking for machine name because current way will show the same name for all OMAP4 machines if they are DT-enabled. Use different way instead

Swirch system/core and device/ti/blaze_tablet to github version · 993b9bf · rbilovol/platform-omapmanifest · GitHub - http://goo.gl/KuvUYb

blaze_tablet: enable device tree booting · d0321e4 · rbilovol/omapboot · GitHub - http://goo.gl/SaHWsR

https://github.com/rbilovol

OMAP: Add ti_shared_gfx_buf shared buffer interface · 196d1f3 · zlatinski/p-android-omap-3.4-android-jb-new-ion · GitHub - http://goo.gl/cUI4ot

OMAP: Add ti_shared_gfx_buf shared buffer interface

ti_shared_gfx_buf is a ION/DMA-BUF buffer wrapper

that adds the following functionality:

Graphics buffer geometry;

Multi-planar support;

Buffer synchronization and reservation support;

The ti_shared_gfx_buf interface is primarily meant for use

by the graphics and display driver and is currently

utilized by the TI's Gralloc module for buffer

allocation and synchronization.

https://github.com/zlatinski

omap: Adds access_process_vm to gpu platform data · 1b372e6 · ariknem/kernel_omap · GitHub - http://goo.gl/B18hQO

blaze_defconfig: Remove SGX driver from blaze_defconfig · 09f71d0 · ariknem/kernel_omap · GitHub - http://goo.gl/wypqFD

https://github.com/ariknem/kernel_omap

https://github.com/TI-OpenLink/device-ti-tablet

https://github.com/TI-OpenLink/kernel-omap
[Samsung Galaxy Nexus] pianistaPL:
I'm waiting for a day when i will can understand at least a few lines of this :(
[Samsung Galaxy Nexus] shriom_manerker:
im up for some hardcore testing as well ;) count me in.
[Samsung Galaxy Nexus] Grarak:
Sounds interesting, but I need to know how to define the second kernel.
[Samsung Galaxy Nexus] RoadToNever:
http://www.androidpolice.com/2014/0...owered-galaxy-note-3-including-kernel-source/
[Samsung Galaxy Nexus] pianistaPL:
Maybe it's a stupid question but which is common Note 3 with GNex?...
[Samsung Galaxy Nexus] bsmitty83:
Pretty much the name Samsung , and android , that's about it
[Samsung Galaxy Nexus] Nephilim:
Not true, they have many things in common:

1. They both have screens

2. They both have batteries

3. They both have completely different f*cking kernel sources that in no way help each other at all
[Samsung Galaxy Nexus] bsmitty83:
If it were only that simple for our poor gnex , lol

In all seriousness , they are light years apart . the biggest problem ,for me anyways is the tuna specific kernel parts do not exist in any 3.4 kernel source . sure it may be omap , maybe even omap4 too , but the tuna board files need to be re wrote for 3.4 , that's a big order especially for me .

We have kernel source , its some drivers , and how the tuna board code interacts with drivers that are missing .

Sucks, yes but as of now 3.0.101 is gonna have to man up and prove its still relevant lol
[Samsung Galaxy Nexus] Vekhez:
I think that [MENTION=5310723]Amperific[/MENTION] was working on re-writing drivers and things.. maybe you and Amp could work together, unless you already are?
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Bookmark this Linux 3.6 repo for the GNeX ;)

A kernel for the galaxy nexus based off of the GNU/Linux kernel. (as opposed to samsung's kernel)

greatDeveloper/tuna-feather-kernel · GitHub - http://goo.gl/cFQc8U
[Samsung Galaxy Nexus] bsmitty83:
Where the f@¢k that come from , cloning this as I type . I wonder if it boots .....
[Samsung Galaxy Nexus] Nephilim:
Omfg! If you get that thing running with SR and Linaro it will be the greatest kernel ever!!!

Sent from my Android 4.4.2 Galaxy Nexus

---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------

Damn dude, you're a f*cking encyclopedia of android awesomeness! Also, I dont believe your part of my G+ Community. Get your ass over there and join the gang. Unless you're already there and I'm just dumb lol.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
It built just about to flash , not sure what's gonna happen since if this booted , it would have been seen already
[Samsung Galaxy Nexus] Vekhez:
Please tell me your fastboot boot 'ing it.. otherwise bricks may happen.
[Samsung Galaxy Nexus] bsmitty83:
Fast boot ? What's that .......:p

May have to wait till morning , I really need sleep and I know if I start digging , i wont stop .
[Samsung Galaxy Nexus] aswinrulez:
[MENTION=4608636]bsmitty83[/MENTION] I dont know how much of help this could be but ill just put it here anyways

http://rootzwiki.com/topic/32023-wi...-36-rc1-developers-needed-a-community-kernel/
[Samsung Galaxy Nexus] AgentSmith:
I hate cliff hangers. ;) Just saying this topic is on the top of my bookmark list! It reads like a good book and I'm convinced there's a happy end.
[Samsung Galaxy Nexus] Utkarsh-ezzo:
[MENTION=4608636]bsmitty83[/MENTION]

have a look here, may be you already have seen it

https://github.com/sonicxml/tuna-feather-kernel/tree/sonic
[Samsung Galaxy Nexus] bsmitty83:
That's what I was looking at / building , it doesn't boot .....yet lol
[Samsung Galaxy Nexus] Utkarsh-ezzo:
That was expected,after reading their thread @ rootzwiki it seems that these are the results of the hard work done by 2 or 3 developers an year ago, they managed to make it compile-able but then it didnt boot and they left it as it is, we all hope you and other devs active here can make wonders happen.

:good:
[Samsung Galaxy Nexus] pianistaPL:
Where is [MENTION=5310723]Amperific[/MENTION] ? :P He could help. Also [MENTION=4615478]boype[/MENTION] but it seems he doesn't have time
[Samsung Galaxy Nexus] bsmitty83:
found the RW page that the creators of the kernel started and its as I thought... dead . but I haven't ran through the code yet , I have no clue what they did to make it compile , what drivers are used etc so itll be a few before I can even figure out if its worth the effort or not
[Samsung Galaxy Nexus] aosp:
I will hit you up on hangouts today cool?
[Samsung Galaxy Nexus] bsmitty83:
Yea link to my g+ is on my kernel op .
[Samsung Galaxy Nexus] aosp:
I'll hit you up soon with info on how to approach this bringup but a straight merge from Google source is the issue and the reason most of the ports have failed choosing to neglect the awesome updates ti devs have made to the omap code will result in failure in any omap4 bringup we must bring the tuna kernel inline with omapzoom 3.0.X first before going for omapzoom 3.4.X gold the omap kernel source on AOSP is way behind and lacking lots of omap4+ enhancements.

I'll tell you more on hangouts soon just know that starting from scratch or creating new board files for the tuna is not needed but modifications to the tuna defconfig and altering of the board files is ;)

[MENTION=4636351]Quallenauge[/MENTION]

I noticed you disabled the new android sync framework on your kernel so I thought you might be interested in the below repo ;)

ti_shared_gfx_buf is a ION/DMA-BUF buffer wrapper that adds the following functionality: Graphics buffer geometry; Multi-planar support; Buffer synchronization and reservation support; The ti_shared_gfx_buf interface is primarily meant for use by the graphics and display driver and is currently utilized by the TI's Gralloc module for buffer allocation and synchronization.

OMAP: Add ti_shared_gfx_buf shared buffer interface · 196d1f3 · zlatinski/p-android-omap-3.4-android-jb-new-ion · GitHub - http://goo.gl/cDI4l6
[Samsung Galaxy Nexus] Vekhez:
You seriously are one big android encyclopedia aren't you.
[Samsung Galaxy Nexus] flip360:
Seriously, me thinks so too :)

Thanks aosp for all the usefull info and godspeed!!!
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4636351]Quallenauge[/MENTION]

Sorry forgot the branch for the new awesome ti omap4+ butter sync frameworks :p

https://github.com/zlatinski/p-andr...id-omap-3.4-new-ion-topic+sync+dma-buf-fence6
[Samsung Galaxy Nexus] nikodr:
This is great :) However i have a question ,i know that it is possible to install a later version of android on phones having kernels that are not updated for it,eg many phones that received ics 4.0 android while they had gingerbread kernels.

Now samsung galaxy nexus has kitkat but kernel is from 3.0.x. What are we actually missing if we use a kernel from a previous era?

Is there something that is not working for gnex?Because all of kitkat apps run with no problems.

Is there something that is present on 3.4 kernels that 3.0.x do not have in the name of features ?

something that would be impossible for kernels in the 3.0.x to have?
[Samsung Galaxy Nexus] pattyboi:):
better gpu support to my knowledge,better performance as well.
[Samsung Galaxy Nexus] mirhl:
[MENTION=2744041]nikodr[/MENTION]

Check kernel changelogs
[Samsung Galaxy Nexus] nikodr:
So that means that since ti developers have had their development for the 3.4 branch of kernel,it would not be impossible to have a working kernel for yakju ant takju toro nexus .

I really hope that soon we could have some new from you guys and a flashable kernel so we could test.
[Samsung Galaxy Nexus] Vekhez:
There is no difference between the Yakju and Takju, it's Maguro, Toro and Toroplus that need looking into, but they all use the same thing anyway a Toroplus kernel will work on the Toro and Maguro, a Maguro kernel will work on the Toro and Toroplus and a Toro kernel will work on the Toroplus and Maguro.
[Samsung Galaxy Nexus] Nephilim:
Or in other words, all Galaxy Nexus variants are considered "Tuna" and every Galaxy Nexus kernel is a Tuna kernel so it is not ever variant specific. ;)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
[MENTION=3685904]ak[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] [MENTION=4112553]dhacker29[/MENTION]

Found a first conversion from old omap DSS to the new omapflb for a omap4460 device the archos a80s

linux 3.0.21 kernel for G9 version 4.0.24 G9 · 0495e0e · Quallenauge/kernel-archos · GitHub - http://goo.gl/aEzxip

Add new thermal framework drivers to allow new PVR drivers, which enable... · 3099980 · Quallenauge/kernel-archos · GitHub - http://goo.gl/QQeGBN

Added display subsystem packages from omapzoom kernel. · 9304e41 · Quallenauge/kernel-archos · GitHub - http://goo.gl/qJuRi8

Adapted archos display subsystem to the TI upstream sources. · 93ec186 · Quallenauge/kernel-archos · GitHub - http://goo.gl/0lovKM

Make use of the new display sub system init routins for additional board... · f2e67f9 · Quallenauge/kernel-archos · GitHub - http://goo.gl/QaM03x

[MENTION=4636351]Quallenauge[/MENTION] Would you be willing to join the effort if we got a GNeX out to you or sent you over some cash? :D
[Samsung Galaxy Nexus] aosp:
[MENTION=4179234]trevd[/MENTION] Same question ;)

[DEV][Kernel] Updated Archos Kernel - xda-developers - http://goo.gl/PT2izY
[Samsung Galaxy Nexus] aosp:
[MENTION=4112553]dhacker29[/MENTION] [MENTION=2581599]FuZZ__[/MENTION] [MENTION=4608636]bsmitty83[/MENTION]

The neglected GNeX lol

Avoid null pointer exceptions by checking vsync period value and reset i... · 69a6e97 · Quallenauge/android_injection · GitHub - http://goo.gl/AeHF7h

HWComposer: Check for zero values before performing division operations. · e0cb5f5 · Quallenauge/android_injection · GitHub - http://goo.gl/GFQKYk
[Samsung Galaxy Nexus] aosp:
[MENTION=3503248]Jiangyi[/MENTION] merged a similar fix for the i9100g recently

fix SIGFPE in hwcomposer caused by modulo by zero · 49fa49c · omnirom/android_device_samsung_omap4-common · GitHub - http://goo.gl/ojhtAC

Looks like the tuna boards are the only omap4 devices using the outdated google omap44xx sources :/
[Samsung Galaxy Nexus] Jiangyi:
Pretty much all other OMAP4xxx devices have been moved up to using PVR DDK1.9 drivers, which in turns means using a bunch of components from omapzoom. I'm not sure of how doable this is on tuna, since the entire graphics subsystem pretty much changed from DDK1.8 to 1.9, and you're going to need other updated binaries (eg. DUCATI, which is likely to be the most problematic) to go along with it.

EDIT: Also, DDK1.9 saw the removal of the kernel-side driver from the Linux kernel. These drivers are available at: http://git.omapzoom.org/?p=device/ti/proprietary-open.git;a=summary, but they require build tree workarounds in order to make them work in an automated build environment without it being placed into the kernel source. Google might not have been able to use these newer drivers due to legal limitations and such.
[Samsung Galaxy Nexus] aosp:
Samsung upgraded the i9100g with the jb update

apply JB update from opensource.samsung.com · 3fcfe76 · CyanogenMod/android_kernel_samsung_t1 · GitHub - http://goo.gl/4XSMGo

archos did it for ics

linux 3.0.21 kernel for G9 version 4.0.24 G9 · 0495e0e · Quallenauge/kernel-archos · GitHub - http://goo.gl/aEzxip

Add new thermal framework drivers to allow new PVR drivers, which enable... · 3099980 · Quallenauge/kernel-archos · GitHub - http://goo.gl/QQeGBN

Added display subsystem packages from omapzoom kernel. · 9304e41 · Quallenauge/kernel-archos · GitHub - http://goo.gl/qJuRi8

Adapted archos display subsystem to the TI upstream sources. · 93ec186 · Quallenauge/kernel-archos · GitHub - http://goo.gl/0lovKM

Make use of the new display sub system init routins for additional board... · f2e67f9 · Quallenauge/kernel-archos · GitHub - http://goo.gl/QaM03x

Google did nothing but leave the tuna with outdated omap44xx software with no omap44xx enhancements whatsoever
[Samsung Galaxy Nexus] aosp:
Also the tuna code in the i9100g kernel source seems to be from https://android.googlesource.com/kernel/omap/+log/android-omap-tuna-3.0-ics-mr1
[Samsung Galaxy Nexus] trevd:
[MENTION=2838735]aosp[/MENTION] I'm afraid I'm going to have to play the lazy bastard card here lol :D

So If you can save me the trouble of reading half the thread the get the gist of things, What was the "same" question?

Thanks
[Samsung Galaxy Nexus] andreas__:
this one, single post above ;)
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4179234]trevd[/MENTION]

https://plus.google.com/106715949401433045760/posts/iKuPgozbyXD
[Samsung Galaxy Nexus] ILA:
[MENTION=2838735]aosp[/MENTION] Are you the maintainer of the official OmniROM builds for manguro? :)
[Samsung Galaxy Nexus] aosp:
No I'm just the messenger [MENTION=4443334]Grarak[/MENTION] got it started and [MENTION=3503248]Jiangyi[/MENTION] got it rolling ;)

[MENTION=4636351]Quallenauge[/MENTION] Have you tried DVP or ARX on the G9?

blaze_tablet: Enable DVP and ARX · 0712ba8 · rbilovol/device-ti-blaze_tablet · GitHub - http://goo.gl/z3UzxL

blaze_tablet: Add ARX and DVP build products · f3d9b63 · rbilovol/device-ti-blaze_tablet · GitHub - http://goo.gl/JWBGSR

blaze_tablet: Change ARX Service permissions · d2200b5 · rbilovol/device-ti-blaze_tablet · GitHub - http://goo.gl/QQVMM2

blaze_tablet: install DSP firmware · 3e04bf6 · rbilovol/device-ti-blaze_tablet · GitHub - http://goo.gl/QeIpXt
[Samsung Galaxy Nexus] trevd:
Hi Folks

I'm nearly done with backporting the internal omaplfb which is compatible with the sgxddk v1.9, I've just got a cheeky null pointer exception to sort out and then it should be good to go. Unfortunately ( for you guy at least ) my hard drive has decided to starting dying so I just need to swap that out before I can continue on this adventure.

In the meantime here's something to tide you over : https://gist.github.com/trevd/8632241

If any one fancies grabbing a shovel then you can dig in here https://github.com/trevd/android_kernel_google_omap using the tuna_defconfig

OMAP4EVA!!
[Samsung Galaxy Nexus] piterdemon:
So what thats mean ? :p I dont understand anything about kernel so if You can write in normal language, please :)

Wytapatano z Galaxy Nexus CM 11
[Samsung Galaxy Nexus] rtfpessoa:
I'm not any expert not even a kernel dev, i know C and i've played with some kernel stuff but nothing hardcore like this.

From what i've seen GN is having massive problems with the video display.

What they are trying to do is update the video drivers and stuff that has to do with it.

With Google i found this:

omaplfb, pvrsrvkm, and bufferclass_ti are the modules that need to be inserted at runtime. omaplfb is responsible for interfacing to the platform specific FrameBuffer driver. pvrsrvkm is responsible for interfacing the user-side PVR services layer. Bufferclass_ti is responsible for enabling a proprietary extension that allows streaming playback through SGX.

So in fact we are closer to have latest PVR drivers running on our GN that will enable better compatibility with recent android and better performance , i think.

Hope this helps explaining :D
[Samsung Galaxy Nexus] shriom_manerker:
basically he almost got the new version of gfx driver (ddk 1.9 whereas old was 1.8 ) to work with our galaxy nexus :)

if you install yahoo weather app and scroll down vertically, youll see scroll lag most of the places. turn it to landscape mode and swype left n right through the cities.. thats how smooth the transition should be :) with the 1.9 drivers. we might be able to see improvement in such minor things. (just assuming this as ive seen the same app on 4.1.2 work a lot smoother compared to all the later versions )
[Samsung Galaxy Nexus] aosp:
OMAP4EVA!! is right finally after all my link posting it pays off lol now all of you #VOTE4trevd cause this is and will be the most important development that has ever occurred on the GNeX since it launched [MENTION=4179234]trevd[/MENTION] thanks a ton for answering my call dude this yankee salutes you and I'm sure all GNeX users here feel the same but we got alot of debugging to do now just send me the bill ;)
[Samsung Galaxy Nexus] aosp:
For those users that have not been following my posts or don't get what is happening or what the big deal is just read my reply on my G+ post ;)

James Dean - Google+ - Galaxy Nexus GSM nightlies are officially live ;) #i9250… - http://goo.gl/cBR5vh
[Samsung Galaxy Nexus] bsmitty83:
I'm curious to how this turns out as I've been stuck just past this point for some time . I've compiled a kernel the same as you with omaplfb moved to video/omap2 , I've built the 1.9ddk module , and replaced all the other binaries , but it does not boot with working display .

Hope you can get farther than I did .:thumbup:
[Samsung Galaxy Nexus] trevd:
I really should have read this thread a little more lol... TBH that sounds like more something to do with your user space libs. can you eleborate ( or should I read the thead :D )

Ideally I've you've got dmesg and logcat of the boot sequence I might be able to push you in the right direction
[Samsung Galaxy Nexus] bsmitty83:
I believe I might still have a log of an early attempt but its been a while since I messed around with this .

Basically from the point your at you need the eurasiacon PVR source , compile that against your kernel , and you'll get a sgx540xx.ko .

You also need the updated binaries , libs . they included both the 540 and 544 libs and depending on what you need it automatically picks the right lib . so naturally all the libs are a different name .

If I can get dome time I'll try to pick this up again and get a good log or dmsg
[Samsung Galaxy Nexus] trevd:
Lol I was going to tell you the samething but meh typing.. Don't worry about that I've sucked a few eggs before today lol :silly:

Did you use the userland binaries from omapzoom? mainly the gralloc?
[Samsung Galaxy Nexus] bsmitty83:
I believe so . they were from a post on this thread by [MENTION=2838735]aosp[/MENTION] . but yes I did try to use the new gralloc as well