Database Users

Confusing GPL/Warez discussion

Hello,
First I would like thank all developers for the wonderful work. It makes the HC tablets very valuable.
I read this forum now for several weeks but the current discussions between the developers about closed source and GPL compliant kernels really confuses me.
Could anyone explain me the current issue?
Currently I understand the issue in this way, please correct me for false statements.
- Thor provides a custom kernel as binaries only.
- The kernel is based on the Android Kernel licensed under GPL
- The source code cannot be downloaded on his website or here in the forum.
My questions are:
- Does the Thor kernel have altered source code lines and functions?
- Is the source code of the Thor kernel accessable by any repository like Git?
- Is the source code of the Thor kernel provided directly after requesting it from the developer?
- How can I obtain the source code I would like to check it?
I would appreciate some facts because currently I am not sure if I could use this kernel for my Iconia or not.
Regards from Germany
Lontro

Lontro said:
My questions are:
- Does the Thor kernel have altered source code lines and functions?
Yes
- Is the source code of the Thor kernel accessable by and repository like Git?
No
- Is the source code of the Thor kernel provided directly after requesting it from the developer?
Potentially. He has said no to others, but it can't hurt to ask.
- How can I obtain the source code I would like to check it?
At present you cannot.
Click to expand...
Click to collapse
Hope that helps

Thank you,
If your answers define the reality than the kernel contravenes arcticle 2b and 3b.
Article 4 would revoke this kernel all licenses. I can´t believe that the developer would risk this.

Several myths have grown up around the GPL v2. Firstly, many people believe that modifying GPL v2-licensed software means that you are obliged to release your modified version to the world. This is not true. The GPL v2 simply states what you must do if you choose to release the modified code. You are at liberty to modify the GPL v2-licensed software in any way you like and keep your modifications for your own private use.
It is also commonly believed that GPL v2-licensed software cannot be bundled with non-GPL v2 software in a collection of software(ex. ROMs with GPL v2 kernels), or that if it is, then all the software must be relicensed under the GPL v2. Again, this is false. Section 2 of the GPL v2 states that such mere aggregations are not governed as a whole by the conditions of the licence.
Finally, it is very common to hear that the GPL v2 (and other general licences) are not binding on the licensee because there is not explicit agreement between the licensee and the licensor. This results from a misunderstanding of the way that such general licensing is intended to function. Section 5 of the GPL v2 expands upon this subject. The copyright of the material distributed under the GPL v2 belongs to the licensor. A potential licensee may not copy, adapt or distribute this material without some kind of licence from the owner. The GPL v2 supplies a route for a potential licensee to legally copy, adapt or distribute the material, provided that they abide by its conditions. Anyone who broke the conditions of the licence and then argued that they had not agreed to them, or that they were unaware of them, would also be arguing that they had no knowledge of a licence that permitted them to use the material in the first place.

I understand that you can modify GPL code without providing it to the public if you use the code for personal reasons.
But if you provide the program in the public you must provide the source code also. Public could be customers only then you must provide it to them but not to the whole world. The Thor kernel is a provided free and in this moment you must provide the source code also. It does not have to be a public access but then the binary download should not be public also.
Novell does not provide their kernel sources to the public of the Enterprise Sles like Redhat does but they provide the source for every licensed customer.
So why should the Thor kernel sources not be provided

Lontro said:
So why should the Thor kernel sources not be provided
Click to expand...
Click to collapse
With respect, there's not a lot of point having this discussion. Thor has been asked many times to release source and has declined. I'm pretty sure we all (including him) know it's illegal, but there isn't really anything that we can do about it.
EDIT: Aside from just not using his kernel, and recommending that others don't either until he makes it compliant.

I think Acer and Google are interested in this issue

In this case the kernel were talking about can be discussed like this:
The licensor is the company who produced the original code distributed under GPLv2 and the licensee is Acer(that posted the source code that was incomplete and buggy) not other developers. That's why all the software that are on this site and others are distributed with disclaimer "we are not responsible for bricking/damaging your device..."
PS: You are not the first nor the last that asks how forums/communities like samdroid... that have software that comes from open source and no source codes.
Code that is added by developer is their property and they decide how its distributed.

themono said:
With respect, there's not a lot of point having this discussion. Thor has been asked many times to release source and has declined. I'm pretty sure we all (including him) know it's illegal, but there isn't really anything that we can do about it.
EDIT: Aside from just not using his kernel, and recommending that others don't either until he makes it compliant.
Click to expand...
Click to collapse
To OP welcome to XDA looks like this is your first post

Has anyone brought this to the attention of GNU? Attached is the URL of their guidlines for reporting. I don't use this ROM so I can't speak to any of these claims.
http://www.gnu.org/licenses/gpl-violation.html
I loathe anyone who abuses the GPL and if he is indeed doing so would like to see him made to comply or punished as much as possible. Another solution would be for XDA to remove his ROM(they don't allow pirated apps afaik, so GPL violations should fall in with that).

muqali said:
Has anyone brought this to the attention of GNU? Attached is the URL of their guidlines for reporting. I don't use this ROM so I can't speak to any of these claims.
http://www.gnu.org/licenses/gpl-violation.html
I loathe anyone who abuses the GPL and if he is indeed doing so would like to see him made to comply or punished as much as possible. Another solution would be for XDA to remove his ROM(they don't allow pirated apps afaik, so GPL violations should fall in with that).
Click to expand...
Click to collapse
The thread about the said kernel was closed by moderator and Thor removed the link of the website from his signature. So basically its out of XDA's hand since the said kernel is not distributed from this site. It's up to the users if they want to use it or not.

I'm not sure where the confusion lies -- a kernel without source is a violation of the GPLv2.
When you are given the source to a kernel, and you distribute a binary form of it, you are required to pass the modifications along.
http://en.wikipedia.org/wiki/GNU_General_Public_License#Terms_and_conditions
The fourth section for version 2 of the license and the seventh section of version 3 require that programs distributed as pre-compiled binaries are accompanied by a copy of the source code, a written offer to distribute the source code via the same mechanism as the pre-compiled binary, or the written offer to obtain the source code that you got when you received the pre-compiled binary under the GPL. The second section of version 2 and the fifth section of version 3 also require giving "all recipients a copy of this License along with the Program". Version 3 of the license allows making the source code available in additional ways in fulfillment of the seventh section. These include downloading source code from an adjacent network server or by peer-to-peer transmission, provided that is how the compiled code was available and there are "clear directions" on where to find the source code.
Full document here:
http://www.gnu.org/licenses/gpl-2.0.html
Even Acer is required to post kernel source:
http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=3851
Not posting source is a violation of the GPL and is stealing other's work. No two ways about it.
I can't think of any good reason not to distribute the source to a kernel that you added a few patches to. /sigh

Micoman said:
The thread about the said kernel was closed by moderator and Thor removed the link of the website from his signature. So basically its out of XDA's hand since the said kernel is not distributed from this site. It's up to the users if they want to use it or not.
Click to expand...
Click to collapse
Unless an organization or kernel developer decides to drop a cease & desist on said author, gpl-violations.org gets involved and/or Acer's legal team decides to get ugly:
http://en.wikipedia.org/wiki/GNU_General_Public_License#The_GPL_in_court
http://gpl-violations.org/

Lontro said:
My questions are:
- Does the Thor kernel have altered source code lines and functions?
- Is the source code of the Thor kernel accessable by any repository like Git?
- Is the source code of the Thor kernel provided directly after requesting it from the developer?
- How can I obtain the source code I would like to check it?
I would appreciate some facts because currently I am not sure if I could use this kernel for my Iconia or not.
Click to expand...
Click to collapse
1. The Thor kernel contains altered source code lines and functions.
2. The source code of the Thor kernel is NOT accessible in any way.
3. As far as I am aware, the source code of the Thor kernel is NOT provided directly after requesting it from the developer.
4. You can NOT obtain the source code.
It will function if installed on an appropriate Acer A500 operating system, but there is no way to know what modifications have been made to it.
See links in my previous posts for more information on how this is a violation of the GPL.
This is the reason why linking to it from these forums is not permitted.
More here:
http://forum.xda-developers.com/showthread.php?t=1159293

jm77 said:
1. The Thor kernel contains altered source code lines and functions.
2. The source code of the Thor kernel is NOT accessible in any way.
3. As far as I am aware, the source code of the Thor kernel is NOT provided directly after requesting it from the developer.
4. You can NOT obtain the source code.
It will function if installed on an appropriate Acer A500 operating system, but there is no way to know what modifications have been made to it.
See links in my previous posts for more information on how this is a violation of the GPL.
This is the reason why linking to it from these forums is not permitted.
More here:
http://forum.xda-developers.com/showthread.php?t=1159293
Click to expand...
Click to collapse
Not sure what's going on in Thor's head, nor why he refuses to comply.
He will be missed though, as he's one of the best DEVs we had for the Iconia

kjy2010 said:
Not sure what's going on in Thor's head, nor why he refuses to comply.
He will be missed though, as he's one of the best DEVs we had for the Iconia
Click to expand...
Click to collapse
If he cared in the slightest, he'd release his code; unless it's doing something it shouldn't.

Now I know enough not to use the Kernel at all.
I did not want to bother this forum with my discussion. Thanx alot.

i know that thor's kernel is krippeld anyhow, there are basic functions in the acer kernel which he has removed, especially the data encryption necessary to make exchange (enterprise) push work with the a500, it will not work without that.
it might be due to the usage of ramdisk, but i am not sure about that.
anyhow as long as he does not implement every function of the original kernel, i will not use his, with or without the availability of the source.
there is a kernel from richardtrip in this forum which works very well has o/c and some other features and has a full implementation of all the original acer functions.
so i really have no need of using thor's kernel, even if he is the best developper in the world.
have fun everybody.

kjy2010 said:
Not sure what's going on in Thor's head, nor why he refuses to comply.
He will be missed though, as he's one of the best DEVs we had for the Iconia
Click to expand...
Click to collapse
He's been saying that m-deejay (the virtuous roms chef) is a thief and liar, hence no (more) source for anyone. this presumably means that he's shared the source before, but not anymore.

edgie168 said:
He's been saying that m-deejay (the virtuous roms chef) is a thief and liar, hence no (more) source for anyone. this presumably means that he's shared the source before, but not anymore.
Click to expand...
Click to collapse
wtf? im thief & liar?
haha
I do not need nothing from his ****ty "source"

genokolar's CM7 rom source missing?

why cm7 source are missing.
@genokolar, is there a problem?
reminding: gnu.org/licenses/old-licenses/gpl-2.0.html

i noticed now. there is no rom with source code! oxygen, miui or cm7. how we can trust these ROMs?

Nobody forces anyone to use any custom ROM, if the ROMS have problems or don't behave as they should, someone would find out (and people post comments every day in the dev section), our devices can be equipped with firewalls, loggers etc so that we can check what happens/happened to our phones during the day.

Oxygen source is available, check the post in dzos thread

cm7 source is in their website, Geno just made port. you can get u8800 device and vendor from other source that are in geno git. if i found - you can too it just very complicated

thanks for all replies.
priestx said:
Nobody forces anyone to use any custom ROM, if the ROMS have problems or don't behave as they should, someone would find out (and people post comments every day in the dev section), our devices can be equipped with firewalls, loggers etc so that we can check what happens/happened to our phones during the day.
Click to expand...
Click to collapse
i now no body force us, but what i want is a situation that should be already.
Tommixoft said:
cm7 source is in their website, Geno just made port. you can get u8800 device and vendor from other source that are in geno git. if i found - you can too it just very complicated
Click to expand...
Click to collapse
good news. but u8800-cm7 not an "official" cm7 port, it should has differences.

Android isn't GPL, it's Apache Software License 2.0. You don't have to make the code available for others and you are allowed to use code but not publish the changes.
So as nice as it would be for Genokolar to share the code, he doesn't have to.

at the end he must hear me.
you are did the right thing.
"knowledge grows by sharing"
thanks Genokolar.

[ROM: DEV] CM7.2 .35 kernel

Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei
My Kernel Source:
https://github.com/PaulMilbank/kernel_huawei/tree/cm7-u8800-35
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul

PaulMilbank said:
Ok, this is just something I have been playing with and thought I would share.
It is CyanogenMod 7.2, as close to stock as I can make it. I have taken a lot from Ezet and some stuff from Forumber.
This is not source based as I do not have a grunty enough system to build CyanogenMod from source.
Most importantly, I have started on a new kernel based on the TomGiordano source here:
https://github.com/TomGiordano/kernel_huawei.git
Will upload my source once I can sort out the sources on my computer. I am doing some mods on Aurora kernel too which I will release at some point.
After a few false starts, I compiled the source with their cyanogenmod_u8800_defconfig and it works pretty well for CM7.2.
I fixed atmel vibration using DZOs aurora commits as a guide.
Probably most broken stuff is defconfig related.
Bugs:
Keypad LED's do not work
Autobrightness does not work
Light sensors do not work- probably the cause of the above problems.
Camera force closes
You tell me
Working:
Wifi works
RIL works
Screen/video drivers work well, screen does not suffer annoying no wakeup for me like other kernels.
Atmel Virtual Key vibration works
You tell me
Get It Here:
http://www.mediafire.com/?b2dc7kdmixvas18
I will try and fix all these bugs, but I would be keen for some help too. I don't have time to be a full time dev.
As always, I am not responsible for any bricks, fires or nuclear wars that come about from installing this rom.
Please, please backup with CWM before flashing this.
Paul
Click to expand...
Click to collapse
Camera issue??? Please, any issues but camera
»»Sent From My U8800««

This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.

PaulMilbank said:
This is just to see if I can get people interested in development. I will try document as much as possible what I do and see if we can get some people interested in building a kernel and getting a really good gingerbread cyanogenmod build out. If this goes nowhere, I will just focus on Aurora kernel and ICS. There are a few things I would like to try and include in Aurora to add some features.
We need good 2.6.35 source and this is a good source with a few small bugs, probably due to the config not being completely right. Hopefully they are minor and easily fixed. We have a lot of kernel development going on around the place and we can learn from commits to make a really good build hopefully.
Will try their 7x30_defconfig to make a kernel for my B528 rom too and see what works.
If you replace the boot.img in this rom with the boot.img in Forumber's latest cm7.2 build, it sould all work and give a 2.6.35 experience close to Ezet's 2.6.32 build. It will likely not be as stable because LEWA kernel on my phone at least, is crap.
Click to expand...
Click to collapse
You can use VictorTeam's source.

forumber2 said:
You can use VictorTeam's source.
Click to expand...
Click to collapse
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.

PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
They have github group https://github.com/Victor-android

.35 kernel based CM7.2 would be pretty dope to me, especially if tethering works

PaulMilbank said:
Do you know where it is, I have not been able to find it. Thanks very much man. Keen top take a look at what they have been doing.
Click to expand...
Click to collapse
here:https://github.com/Victor-android/kernel_huawei/tree/2.6.35-cm-u8800

Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!

PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Nice to hear that someone's still working on U8800's .35 kernel. Good job so far!

PaulMilbank said:
Thanks, this will likely take a while longer than I thought it would as I am having trouble getting my sources synced locally and on github. If we can pull together all the sources into a kick ass kernel, we should have a really good CM7.2, I would like a rom with built in tethering too. It will just take some time. Running through DZOs excellent repo with a readymade .config and then making small changes is a lot easier than having to make it all up as we go and sort out sources and configs. Maybe I should not have been so cocky at the start!
Click to expand...
Click to collapse
Do you use your vendor files for compiling CM7?

forumber2 said:
Do you use your vendor files for compiling CM7?
Click to expand...
Click to collapse
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!

PaulMilbank said:
No, I am just using your and Ezets prebuilt binaries and apk's. I do not have the computer power or skill to build from source!
Click to expand...
Click to collapse
But you could compile kernel?

Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium

PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
Will you try your luck with cm9/10?

PaulMilbank said:
Compiling and downloading kernel is much smaller and faster. Also their are a lot of comments and files to follow.
Compiling cyanogenmod from source is a huge download and would take forever to compile on my computer. Plus nobody documents the process well and it us specialized to the phone.
Maybe if I can get a good kernel going, others can build cyanogenmod sources for .35 kernel. It all just takes time.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
if you send vendor files to me,i can compile in my free time

forumber2 said:
if you send vendor files to me,i can compile in my free time
Click to expand...
Click to collapse
Maybe Ezets here:
https://github.com/ezeteze/android_device_huawei_u8800.
Not sure otherwise. I don't have any vendor files sorry.

Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.

Unrealized said:
Use these vendor files: click. I built CM 7.2 yesterday and it works just fine with those vendor files.
Click to expand...
Click to collapse
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:

forumber2 said:
but in this vendor,GPU can't run fully,has a little lag. If we solve this problem,we can make a good cm7 :good:
Click to expand...
Click to collapse
Guess it has something to with the "new" Adreno drivers. Might do some benchmarking later with the older ones. I haven't really experienced lagging myself though. it's kinda the same as w/ .32 based CM7 (especially when using ADWLauncher)

[REQUEST] N8000 Kernel Source

I am about to build a kernel for N8000. But my problem is I can not download from samsung open source site (Very Slow Connection).
Can someone please mirror the update7(MD1) for me on a fast server like dev-host, android file host, mediafire or etc...?
Here's the Samsung open source site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8000
Thanks in advance.

You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.

kcrudup said:
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
Click to expand...
Click to collapse
Thanks.
I have two questions if you don't mind.
1. Merge-to-ss-jb is the latest source (MD1)? Is it a good to go for a kernel to be based upon?
2. Is it alright with you that I base my kernel on your own kernel?
I appreciate it if you can help me with some kernel stuff as I am new to this.
Sent from my HTC One X using Tapatalk 4 Beta

csec said:
"merge-to-ss-jb" is the latest source (MD1)?
Click to expand...
Click to collapse
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Is it alright with you that I base my kernel on your own kernel?
Click to expand...
Click to collapse
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.

kcrudup said:
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
Click to expand...
Click to collapse
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD

csec said:
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Heard that the published sources have different wi-fi drivers than preinstalled stock kernel.
This is the main reason of allshare cast not working with custom kernels (on the contrary, some s3 custom kernels DO SUPPORT allshare cast), even if status=official and flash counter=0.
Anyone can confirm?
Anyone has the proper ones or know which one (i.e. from a different samsung device) to use?

gitHub link dead

4.3 kernel sources released! grab them here

http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/

Wow man latest news isn t it?? Using Internet Explorer??

And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk

It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app

Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?

ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?

What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?

granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse

dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited

granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.

rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.