I'm running a bounty for Audience chipset support in re-oriented kernels. I will personally paypal you $50 if you can provide a working GB I9000 reoriented kernel ( and instructions for the rest of the devs ) with working Audience support.
I will keep a list of any further donations here -- I am not responsible for any other donations other than my own.
I haven't done any Android kernel development other than browse the files from time to time. Coming from the linux/freebsd world from what I've seen this should be technically feasible:
The kernel ABI doesn't change much from 2.2 to 2.3 .. if at all:
Kernel:
Android 2.2 – Linux Kernel 2.6.32
Android 2.3 – Linux Kernel 2.6.35
One should be able to simply 'graft' audience enabled makefiles/src/objects/options etc into any kernel build from the captivate 2.2 release on Samsung's opensource site with minor edits.
Additional Contributors:
RichMD $10
othermark said:
I'm running a bounty for Audience chipset support in re-oriented kernels. I will personally paypal you $50 if you can provide a working GB I9000 reoriented kernel ( and instructions for the rest of the devs ) with working Audience support.
I will keep a list of any further donations here -- I am not responsible for any other donations other than my own.
I haven't done any Android kernel development other than browse the files from time to time. Coming from the linux/freebsd world from what I've seen this should be technically feasible:
The kernel ABI doesn't change much from 2.2 to 2.3 .. if at all:
Kernel:
Android 2.2 – Linux Kernel 2.6.32
Android 2.3 – Linux Kernel 2.6.35
One should be able to simply 'graft' audience enabled makefiles/src/objects/options etc into any kernel build from the captivate 2.2 release on Samsung's opensource site with minor edits.
Click to expand...
Click to collapse
I haven't personally looked into them, but I know Atinm had looked at it, and apparently there was quite a few changes involving audio stuff, including the audience chip drivers.
Not saying it can't be done, obviously, but I don't think its a simple copy/paste action either.
I'd throw in $10
Sent from my GT-I9000 using XDA Premium App
Related
Been a while since my last post
is there any modified Kernel for the Tab ? I've seen a Galaxy S runs like a fart on youtube " 1.6 Ghz "
my question is : is this kernel adjustable for the tab ? is there a running project in XDA to make this happen ?
thanks a lot
I have compiled both the AOSP (Android Open Source Project) and the Samsung Galaxy Tab open-source code, but I'm happy with JM6 so far, and I guess I am not brave enough to flash self-compiled critical components, I had enough problems with just self-compiled apps
flashed self compiled kernel resulted in panic
I flashed a the open source basekernel with the galaxy patch from samsung and got no joy. Nothing but kernel panic. Fortunately I was able to flash the original zImage back. Any insight on configuration parameters to use. I just did a stock make.
How did you load the system.img and data.img out from AOSP? I've compiled and can't figure out how to load the images.
Thanks
Im actually going to wprk on making a kernel oc'd just need a few tips ive done linux kernels before but the difference is i dobt have the source does anyone have the source to sprints firmware?
Sent from my SPH-P100 using XDA App
If anyone actually releases a stable 1.5GHz or higher kernel, I'll definitely donate $50 for the work, and I'm sure others will too.
I hope Tytung doesn't mind me posting this up but I just wanted to inform everyone that he has just released his Kernel source for ICS so devs can help on the development for the fellow HD2. From his post:
tytung said:
As promised, I have uploaded my latest ICS kernel source to the GitHub website.
https://github.com/tytung/android_kernel_htcleo-2.6.32-ics
I changed the kernel name to ics_htcleo_r1, a neutral name.
If anyone really want to help improve this ics kernel, please fix/add the following features first and consider sending me a git pull request.
Full Hardware Acceleration.
Proper hardware encoder for camcorder to record the smooth video.
More compatible touchscreen driver for ICS to fix pinch-to-zoom issue.
Proper VPN driver for ICS.
I uploaded my kernel source to the git mainly for the collaborative development.
In other words, don't add small stuff based on this kernel and then release a new kernel with your own name.
Thank you for your cooperation!
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/showpost.php?p=22607800&postcount=3292
If any devs could help the further development of this Kernel that would mean a lot to the HD2 community Please give all your thanks to Tytung for all his hard work
Good job
Thank you tytung !
can someone update .597 kernel here is source
https://github.com/kamarush/semc-kernel-msm7x30-3.0.8
https://github.com/nexx/htc-kernel-msm7x30
also cyanogen start porting 3.0 kernel for msm7x30
http://pocketnow.com/android/cyanogen-porting-linux-30-kernel-to-msm7x30-phones
thers some sorce i just googleing and found this
ps i alo find this : https://github.com/kamarush/semc-msm-3.4
According to a Google+ post (what are we going to call those? Geeps?) Cyanogen himself is working on porting the Linux 3.0 kernel to Android-powered devices running on the msm7x30 chipset.
According to the post “All the subsystem changes from 2.6.35 to 3.0 are super tedious, especially sound.”
What does the 3.0 kernel include?
First of all, it does NOT include any “special scary new features” and “there’s absolutely no reason to aim for the traditional ‘.0′ problems that so many projects have”.
Instead the release includes the “usual two thirds driver changes, and a lot of random fixes” and “some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!)”.
According to Linus himself, “in general this is supposed to be a fairly normal release cycle”.
So, with no much fanfare, the 3.0 kernel was released, and with the backing of one of the Android greats, it’s coming to smartphones soon.
Click to expand...
Click to collapse
Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2