DVB Drivers for M-Kernel mr1 - Nexus 7 General

I cannot reply to the M-Kernel Annoncment, but I thought maybe somebody else could use these DVB drivers. The only ones I found precompiled on XDA were for old Kernels

Related

[MOD] BlaY0's kernel 2.6.29 with UTF-8 NLS support + additional modules

Hi,
I decided to post here two kernel updates I mainly use or have used on my Legend. They are nothing special (not overclocked), with several additions and changes, just something I want to share with the Legend scene. They corespond to two different (stock) extraversions:
2.6.29-5f084974
Based on stock HTC kernel version 13be9c9c available from their Developer Center. The kernel is perflocked by default (123-246 MHz screen OFF , 246-600 MHz screen ON, 123-600 MHz scaling for ondemand governor). Modules (drivers) included:
aufs.ko (overlay file system driver)
cifs.ko (CIFS file system driver)
cpufreq_conservative.ko (conservative scaling governor)
cpufreq_interactive.ko (interactive scaling governor)
cpufreq_powersave.ko (powersave scaling governor)
lzo_compress.ko (lzo compressor)
lzo_decompress.ko (lzo decompressor)
perflock_disable.ko (forcibly disables perflock)
ramzswap.ko (Compcache driver)
sdio.ko (TI SDIO driver)
squashfs.ko (SQUASHFS 4 file system driver)
tiwlan_drv.ko (TI Wlan driver)
tun.ko (TUN/TAP driver)
ext4.ko (ext4 file system driver)
jbd2.ko (ext4 dependency)
lockd.ko (NFS)
nfs.ko (NFS)
sunrpc.ko (NFS)
2.6.29-8d705e0d
Based on CM's 2.6.29.6 GIT with some additions from Alex's GIT. Specs are the same as for above version.
UTF-8
As an option, I also prepared two kernels same as above but with UTF-8 NLS support set as default.
Installation
Just flash the update via ClockworkMod... it will run over your previous kernel and modules.
Note
These kernels are ment for those using stock based ROMs (like chefs using stock ROMs as a base) and are missing support for things mentioned above (nfs, aufs, cifs, tun, interactive governor...). Those using CM based ROMs don't need any of these... CM already has kernel with all support mentioned above.
Warning!!!
Please read the whole post before you download (it's really not so long)! Do not apply these updates if you don't know what they actually do!
Hello,
this one : 2.6.29-8d705e0d doesn't work with Azure Nightly 8.
The touch screen don't work !
vadatte said:
Hello,
this one : 2.6.29-8d705e0d doesn't work with Azure Nightly 8.
The touch screen don't work !
Click to expand...
Click to collapse
Build 8 quite bogus, random reboots and non working TTS
have you tried with build 7?
I have similar problem with Azure Nightly 7 and Kernel 2.6.29-8d705e0d
Touch screen don't work !
Probably I should've mentioned that these kernels have been primarily ment for stock based ROMs.
I don't get it guys... I believe I mentioned in 1st post that second kernel is based on CM's so why would one ever want to us my kernel with CM... CM already has the right kernel with all the modules and statically built support for anything I mentioned above.
If you guys are trying nightlies expect problems but most important learn how to debug them. If you just write that it doesn't work, you basically did nothing to help solving the problem or improving things.
One more thing... did you guys try dumfaq's OC kernels with those CM nightlies?
Sent from my HTC Legend using XDA App
BlaY0 said:
If you just write that it doesn't work, you basically did nothing to help solving the problem or improving things.
One more thing... did you guys try dumfaq's OC kernels with those CM nightlies?
Click to expand...
Click to collapse
With Azure Nightly 7 the phone starts correctly, I can not use the touch screen (it's impossible to navigate with my fingers )
And no I don't try dumfaq's OC kernels with cyano nightlies.
I would like to say something:
If you don't have any idea what these kernels actually change, then don't use them. There's no point in going "Duuh, BlaYo made a kernel, it must be awesome! I'll use it", when you don't know the advantages of using them. This kind of thing goes for a lot of stuff on these forums. If you don't understand what it does, or if you wouldn't know where to start with debugging errors, then either don't use it, or do research and make an informed decision on whether you actually need it.
And this goes for yez nightly users, too: nightly builds are almost never better than the stable. If you want CM, use Azure, not the nightlies. Unless of course your doing real testing, debugging and then feeding it back to CM developers.
Exactly!
Sent from my HTC Legend using XDA App
BlaY0 said:
Exactly!
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
We live and learn.
Request: nls_utf8 module please.
Hello BlaY0, Thank you for you posting the kernel.
I am enjoying cifs with your 2.6.29-5f084974 on Azure, thank you!
Would you please add one more module "nls_utf8"? This helps converting filenames written in lot of languages other than English.
That can be arranged. But I have a question for you. What's keeping you from compiling it yourself? Since you know what those modules are for, I'd suspect you have done it before... at least for x86 architecture?
Thank you for your reply!
I am sorry, I've not tried it yet, only read FAQ #2 in "CifsManager" created by f3d0r.
forum.xda-developers.com/showthread.php?t=756158
Q: I mounted my favorite share successfully but files with special characters are not displayed correctly.
A: Try to use a kernel with explicit UTF-8 support or try to find/load the kernel module nls_utf8.ko via a simple init script.
Click to expand...
Click to collapse
May I try it with your help?
Hi BlaY0, please hold my request.
I found your message at "[Q] Custom Kernel" thread. I will try by myself with kyosa's config. Thank you!
Check this one too...
I added nfs support to 1st one and ext4 to both. I also prepared optional kernels (same versions) with UTF-8 NLS support set as default.
My two cents:
For a few of these it doesn't really make sense to compile them as modules. tun, lzo, utf_nls don't really bloat the kernel or negatively affect performance for example.
I know... I just put them here because you can freely extract them and use them with plain (not modified) stock kernel. That's why I'm using stock kernel extraversions and not my own.
As for NLS it is already statically compiled (not as modules) in those two kernels...
Hi BlaYo, Thank you for your new kernels! "5f084974" kernel and modules worked perfectly with Azure1.01! I can now read any filenames on my file server. I am so happy!!
Ah-- Yes, last weekend I gave up. I could not make wifi active...
(Of course, I re-compiled tiwlan_drv.ko) So I gratefully accept your favor.
Hello Ali ba!! Thank you, I found "nls_utf8" was already enabled in your nightly build. (I saw in config.gz) I am sorry I've not test them yet. I will test and report about this!

Official kernel vs Android kernel

Is it possible to use the official kernel sources to compile a kernel for the HTC Dream (G1)? I'm going to assume not but I find it interesting that there is an option for the HTC Trout/Dream for the CPU architecture.
FourM said:
Is it possible to use the official kernel sources to compile a kernel for the HTC Dream (G1)? I'm going to assume not but I find it interesting that there is an option for the HTC Trout/Dream for the CPU architecture.
Click to expand...
Click to collapse
How about before anyone answers, you please define what you mean by "official kernel sources"... because this can be taken to mean a LOT of things.
exactly what it means. Sources coming directly from www . kernel . org for a general linux distribution.
I doubt you can use straight linux kernals on android because of the nature of how android works (with the java app layer above linux and such) but what does a noob like me know

[Q] How to set up O2X kernel/rom build environment?

For a few days now I've been trying to set up a build environment to compile (for starters) the stock kernel on my own.
I'm using Ubuntu 11.10 x64 and have tried to build an ARM EABI capable GCC using
vorkChain script
Linaro GCC
without success. Everytime the compilation process aborts with either libstdc++ missing ('/bin/bash: line 3: cd: arm-eabi/libstdc++-v3: No such file or directory') or some error with the strip command.
I'm now trying to get running with the sourcery toolchain but I'm unsure if that's the right direction or if it's just compiling a Tegra2-compatible but not optimized code.
How did you set up your build-environment for the LG-P990 kernel/ROM development?
Hello!
Did you read this guide!?!
http://forum.xda-developers.com/showthread.php?t=1104523
Did you follow this thread!?!
http://forum.xda-developers.com/showthread.php?t=1118091&page=4
Thanks for the hints. I had a look at both but unfortunately they are targeted at CM7 builds which have a specific and defined environment/structure, use loads of scripts to set up all requirements and would require me to download several GBs (~20GB?) just to begin working. Furthermore the guides require me to flash CM7 on my phone as at one step they extract propietary stuff from the phone to have a successful build. That's not exactly what I'm looking for.
What I'm looking for is a description on how to set up the compiler (+dependencies) environment which allows me just to build the official kernel on my own. I tried to get some hints out of the CM scripts but with no luck. All my searches in the forum also have been not successful.
Maybe someone more experienced than me can give me some info or hints on topics which could help me with my search?
Hello!
Well, I am not an expert in kernel-build myself but there where discussions in the ironkrnL threat and some people managed to build kernels from the devs github their (i.e. vodonka)...
Beginning somewhere here…
http://forum.xda-developers.com/showthread.php?t=1359307&page=33
And I found this…
http://www.mydroidworld.com/forums/...-how-compile-cyanogen-gingerbread-source.html
The HowTo from Cyanogen is for Debian and Red Hat…
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
…but it doesn’t say much about compiler setup itself anyway.
The best thing might be asking one of the people building kernel-Kangs frequently like rusty, temasek or koboltzz.
Medizinman I think you still don't understand, you keep giving links for cyanogen kernel!!
There is no way to compile stock kernel with cyanogen environment.....
Kosi you should ask for Spica and Koboltz in dev section they build stock kernels.
Hello!
Oh sorry, I overlooked this... ...of course he can't build a "stock kernel" from Cm7-source...my fault/mistake.
...forget what I wrote...
Yes, asking one of the "stock-kernel-devs" on xda like Spica (hp kernel for stock), Koboltz, Imperticus(NeoBlaze kernel) or dr4go (fps kernel) might be a good idea indeed...
Medizinmann said:
Hello!
Oh sorry, I overlooked this... ...of course he can't build a "stock kernel" from Cm7-source...my fault/mistake.
...forget what I wrote...
Yes, asking one of the "stock-kernel-devs" on xda like Spica (hp kernel for stock), Koboltz, Imperticus(NeoBlaze kernel) or dr4go (fps kernel) might be a good idea indeed...
Click to expand...
Click to collapse
Hi all,
Does any one have compiled kowalski kernel from sources (github(dot)com/pengus77/lge-kernel-star) ?
I have been using Linaro toolchain 4.6.2 to compile it, and it build ok. However, I can not boot using the generated zImage - it always stucks in the LG logo.
Can you give me some pointers concerning the compilation flags and/or environment?
Thanks!

[driver/libs][jelly bean adreno 2.x.x libs from xperia play]

Here are drivers for ICS/JB from the Xperia Play forums.
Can this do any good for games (HD games?) As far now I am on cm10. All is working well . I do not want yo get screwed up now. If this will for sure improve gaming performance I would like to tty. But please advice this will not effect other performance......
Sent from my A99 using Tapatalk 2
leoaeries said:
Can this do any good for games (HD games?) As far now I am on cm10. All is working well . I do not want yo get screwed up now. If this will for sure improve gaming performance I would like to tty. But please advice this will not effect other performance......
Sent from my A99 using Tapatalk 2
Click to expand...
Click to collapse
Backup CWM first
Sent from my Spice Mi-410 using Tapatalk 2
I don't think this will work, because as far as i know these are not actually drivers but shared objects *.so (much like dll files in windows). The gpu drivers are actually compiled within the kernel and the version of these *.so files must match with the version of the gpu drivers compiled within the kernel. So unless those match i don't see these working for us. However i may be wrong, devs can throw more light on this.
nayneshdev said:
I don't think this will work, because as far as i know these are not actually drivers but shared objects *.so (much like dll files in windows). The gpu drivers are actually compiled within the kernel and the version of these *.so files must match with the version of the gpu drivers compiled within the kernel. So unless those match i don't see these working for us. However i may be wrong, devs can throw more light on this.
Click to expand...
Click to collapse
Actually all version of CM7 / CM9 for Motorola Triumph, and edowar's have not been built from source. All files have been copied over and built with the source code. Here is a few examples of the code copying
CM7 MTDEV
https://github.com/MTDEV-CM7/vendor/blob/cm7/motorola/triumph/triumph-vendor-blobs.mk#L82
CM9 MTDEV
https://github.com/MTDEV-CM9/vendor/blob/ics/motorola/triumph/triumph-vendor-blobs.mk#L206
CM9 edowar
https://github.com/edowar/android_device_fb0/blob/ICS/device_fb0.mk#L230
Yes i understand that. But afaik edowar had built a 0.32 kernel with newer gpu drivers which is used in bumblebee rom ported from whyzor's cm7. If u use the same gpu drivers(*.so) in any other 0.32 based rom then they won't work without using the same edowar kernel. And i think the sources for more recent gpu drivers are taken from code aurora forum.
Sent from my FIH-FB0 running fantastic gingermia (which needs an update) using xda app-developers app.
leoaeries said:
Can this do any good for games (HD games?) As far now I am on cm10. All is working well . I do not want yo get screwed up now. If this will for sure improve gaming performance I would like to tty. But please advice this will not effect other performance......
Sent from my A99 using Tapatalk 2
Click to expand...
Click to collapse
Hey leo,
What HD games can you play on our ICS and JB ROMs?
Thanks.
^_^
nayneshdev said:
Yes i understand that. But afaik edowar had built a 0.32 kernel with newer gpu drivers which is used in bumblebee rom ported from whyzor's cm7. If u use the same gpu drivers(*.so) in any other 0.32 based rom then they won't work without using the same edowar kernel. And i think the sources for more recent gpu drivers are taken from code aurora forum.
Sent from my FIH-FB0 running fantastic gingermia (which needs an update) using xda app-developers app.
Click to expand...
Click to collapse
You are correct there is some changes for those specific drivers based on the kernel (forgot to mention that ) here is the commits needed for the kernel
https://github.com/Whyzor/WX_435_Kernel-CM7/commits/master
Look at all the commits from Mar 01, 2012 and that will get you in business with those specific drivers.
Actually these libs work fine. tested in cm10 and cm9 for our device
nachiketa.ramesh said:
Actually these libs work fine. tested in cm10 and cm9 for our device
Click to expand...
Click to collapse
If the libs work fine then, i don't expect any differences, cause the versions will be the same.

[Q]how to compile from source

I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
bomdia said:
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
Click to expand...
Click to collapse
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Lexmazter said:
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Click to expand...
Click to collapse
thanks a lot I think I start tomorrow I'm a little tired
Hi just so you know you won't be able to compile Paranoid Android for ICS from source as it was never released.
If you can get JB to work then you will not only be a hero but also be able to use Paranoid Android source
I have a problem I can not download the sources of the paranoid in any way
help (or build the sources normal Android?)
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Post link to guide.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
bomdia said:
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Click to expand...
Click to collapse
I do not recommend Linux Mint 14 as it is new edition, based on new Ubuntu version 12.10 if i remember good, don't know for sure, that's why, on Ubuntu 12.04 building is supported, even though on some guides it is said that on 12.04 it is experimental, well, it was, now it should be stable.
Also, if you want to port things like Paranoid or PAC you should start with AOSP or CM9 or AOKP, to put it short, versions that have guides and source codes on their sites. In my opinion CM is the best thing to start with, that's why i started CM9, after that you can easily port every 4.0.4 AOSP based ROM.
The same thing applies to JB, if you can port or build AOSP or CM10, you can port every JB AOSP based ROM very easily following only a few basic steps, that's how things work in this hood
Off-topic: I was a little distracted from building/testing/devving because of the school affairs, but today i will resume my work on CM9, if things work well, i will have a bootable build this very evening.
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
anders3408 said:
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
Click to expand...
Click to collapse
5941 no OC with LTX Kernel v0.7 and Sense 3.0 by fshami, also, i think i found the right ramdisk for now for CM9, it solved the dalvik-permissions, now i still need to boot the build, still trying to figure what is wrong here and why it hangs after Android is upgrading... >> Starting applications.
I can work more on my device now as i have a cheap second phone to use if for calls and sms.
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
bomdia said:
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
Click to expand...
Click to collapse
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Lexmazter said:
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Click to expand...
Click to collapse
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
bomdia said:
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
Click to expand...
Click to collapse
Well, i recommend this because i'm still building 4.0.4 and i haven't successfully booted a build, so that's why i say this, because if you get the 4.0.4, in short terms, all you need to change for 4.1 is the graphics driver, but for 4.2 i don't know for sure, too new for me and i'm still trying to get 4.0.4 to air
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
anders3408 said:
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
Click to expand...
Click to collapse
just enter the irc channel, will talk more there, no need to spam the forum with this.
The boothanging is because of the audio, the ramdisk is good, i use the LTX v0.7 zImage and ramdisk from stock edited to fit the build.
Also, the ramdisk is not made with the build, maybe if you compile the kernel with the rom, and for this you need to put the kernel online and othe things, and because of proxy, i can't and won't do that. For more details, like i said, find me on the irc.
link here
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
bomdia said:
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
Click to expand...
Click to collapse
yeah, those are the drivers
But they do not require a new kernel
Lexmazter said:
yeah, those are the drivers
But they do not require a new kernel
Click to expand...
Click to collapse
but I need or I do not need?

Categories

Resources