I don't know if this might be useful for devs, but since the Linux kernel is open source, i guess it might help a little.
Link do the post: http://www.phoronix.com/scan.php?page=news_item&px=MTIyNTc
Staging stuff is the 'corner of crap' of the kernel - beta stuff which does not meet the quality standards of the kernel. In other words, those drivers won't be fun until they stabilize a bit.
Either way problem with atrix is not that we can't use current closed sources drm drivers but that we have to make kernel with support for all internals of atrix like buses, controllers and other devices. And then connect all things together with correct frequncies, voltages, pinmuxes. That makes things hard. Especially because things in 2.6.32 were done dynamically and it's hard to read it from code. Yet I'm working on that
Sent from my MB860 using xda app-developers app
for now, seems to exist no 3D support. But I believe that this mature driver can serve to help.
First someone would have to port our kernel to 3.8 or downport drm driver from 3.8 to 2.6.32. Sooner we'll have port to 2.6.34.9 and HWA.
Sent from my MB860 using xda app-developers app
3.8 ? I think our tablet has 3.08 kernel
It may have 3.0.8. As for 3.8 it's not even released yet, we have now 3.7 as an unstable/development version of 3.8, and Nvidia's DRM driver integration is planned for 3.8. And even then it's not gonna show up in android soon, as android kernel is not fully integrated with mainline kernel yet. So looong road till we have something we can call stable and usable. For now open DRM drivers don't have 3D support, so it basically leave us here where we are currently. It's nice Nvidia is working with opensource community, but these drivers are mainly for embeded tegra2 based systems (like in cars or washing machines). I'm not saying it can't be used in our phone, but you won't gain much. Unless there is Android 7.0 and nvidia no longer supports tegra2 platform and we want it badly then we can use it (i think).
Related
http://www.phoronix.com/scan.php?page=news_item&px=MTIzNTQ
If this ever gets ported to andorid it could mean indefinet open source suport for our SOC, or native linux (X11) on our phones. looots of work remaining thow
This could mean some good old webtop on ICS. X11 is a window manager, the one used for Webtop 2.0. Or maybe this could mean some great mods for the current Webtop 2.0. :fingers-crossed:
there is currently a Q&A with an ARM GPU division VP at anandtech.com , where we can raise awareness about the MALI GPU's lack of open-source drivers (the main reason why were all getting bad/****ty CM support here..)
so raise you voice ! get yourself heard ! its the only way this works.. and maybe, just maybe .. these godamn bastards will realize you cant keep calling yourself "open" and not release open-source drivers for linux and android !
http://www.anandtech.com/show/8226/ask-the-experts-arm-fellow-jem-davies-answers-your-gpu-questions
Thanks
Enviado desde La Isla de Camaron
Exynos sources would be much more useful.
we are getting bad support because 60% of our drivers aren´t open source and are from Samsung, witch modifies to run better touchwiz than aosp, mali´s drivers are already good running aosp,i have a tab with a mali gpu and it runs aosp without no problems, good support and speed.
our main problems are that since we dont have open source drivers(just a few) we have to modify the rom to runs with our drivers, alongside we still run at 3.0.101 kernel,witch not even jellybean fully supports it(jb is made to 3.1+).
TL;DR whats the point of having just the gpu driver that is already pretty good/optimized for aosp and not having the full soc sources?even more the exynos one, since its optimized for touchwiz, not for aosp.
Exynos 4 is one of the most closed-source SoCs ever created till now. One driver won't change anything, deal with it. SGS3 is closed as hell, we're lucky that AOSP is pretty damn acceptable in current form.
The big hype surrounding Android L’s unveiling caused us all to skip one important change, the debut of the Linux 3.10 kernel in the ARM world.
If you take a closer look at defconfigs, you might notice that there are some experimental configs available for various platforms. For example, there are files with configs for MSM8974 architecture, widely used in various flagships like the OnePlus One, HTC One (M8) or Google Nexus 5.
Click to expand...
Click to collapse
[XDA]
Kernel 3.10, the long term release that Google is going to use, will add even better ARM and 64 bit support, more improvements to the F2FS file system, better virtualization support, better encryption support for ARMv8 chips (which can encrypt stuff with AES up to 10x faster compared to the ARMv7 architecture), and lastly support for big.Little chips.
Click to expand...
Click to collapse
[Androidheadlines]
Linux kernel 3.10 has added support for big.LITTLE processors, which should help developers port Ubuntu Touch to the Samsung Galaxy S4 and other devices.
Click to expand...
Click to collapse
[Phonearena]
Qualcomm MSM8226 (Moto G) config also available.
GIT: https://android.googlesource.com/kernel/msm/+/android-msm-dory-3.10-kitkat-wear/arch/arm/configs/
that is fantastic. if moto g is considered in this kernel then we will have full featured android l with proper kernel.
Great news! I was wondering if they were going to update the kernel in the L release and was a little dissapointed to see 3.4 in the preview.
Could have been better though, it´s still more than a year behind mainline.
With further f2fs improvements, a performance gap between GPE and other models may become more obvious. Unless of course, Google make GPE f2fs also with Android L.
lost101 said:
With further f2fs improvements, a performance gap between GPE and other models may become more obvious. U
the latest f2fs patches are already in come of the custom kernel and i dont feel a thing (could new format will bring some improvement?)
good possibility that f2fs could be default. Although new kernel is good news, i was hearing that the latest kernel will be fully inline with main kernel and will be most uptodate. they have again taken the stable base approach. a tad disappointing.
Click to expand...
Click to collapse
lost101 said:
With further f2fs improvements, a performance gap between GPE and other models may become more obvious. Unless of course, Google make GPE f2fs also with Android L.
Click to expand...
Click to collapse
Changing the filesystem requires a full format, I doubt devices will just get that over the air...
Sent from my XT1033 using Tapatalk
vlt96 said:
Changing the filesystem requires a full format, I doubt devices will just get that over the air...
Click to expand...
Click to collapse
Good point, and that's probably what will happen. GPE will continue to use EXT4.
Asking the average user to accept a complete data wipe would be a hard sell, even with cloud backup.
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
v1nsai said:
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
Click to expand...
Click to collapse
I wish someone could answer this because I'm considering one of the new Nexus devices because I thought I could have this best of both worlds that he speaks of. Is this not the case, do open source driver devices like Nexus phones suffer with the same issues as other unlocked phones that have closed source drivers?
https://github.com/BalcanGSM/MediaTek-HelioX10-Kernel
https://github.com/BalcanGSM/MediaTek-HelioX10-Baseband
Not complete sources.
Just curious, what's missing to be able to build a kernel from that repo?
edit: actually, nvm.
Could someone check sources for Sony Aqua M5? It has the same CPU.
http://developer.sonymobile.com/dow...1-33-30-0-b-1-33-30-0-a-1-35-and-30-0-b-1-35/
Crim Soukyuu said:
Just curious, what's missing to be able to build a kernel from that repo?
edit: actually, nvm.
Click to expand...
Click to collapse
yep, did someone actually check what is missing?
I mean, display drivers .. the drivers for the sensors which are not part of the SoC, such as Lux, camera drivers.. what else?
I am quite sure that looking at the manufacturer´s sites of these components, more drivers, or at least documentation how to drive the components could be found?
Please help to sign this petition
So we can get kernel source for this device.
https://www.change.org/p/xiaomi-inc-mi-com-hugo-barra-release-kernel-source-from-xiaomi-redmi-note-2
Thanks
Sent from my Galaxy Nexus using Tapatalk
How about this? https://github.com/jawad6233/MT6795.kernel
icedeocampo said:
How about this? https://github.com/jawad6233/MT6795.kernel
Click to expand...
Click to collapse
The same. Read the previous messages
~ Xiaomi Redmi Note 2 Prime ~
All these sources are only good to someone who wants to get familiar with mt6795 or MTK in particular,
however just because some source/phone has the same chipset doesn't mean much.
What we're interested in are the drivers and configs for the sensors/components used in a particular device.
So a generic source is of no use if you don't have those drivers and an average Joe can't find them on github,
especially on a new phone which does not share the same sensors as some older device.
Eventually you can get some of the configs by reverse engineering the stock kernel and many many sleepless nights,
but without the actual drivers (or at least something similar that you can base your work on) your hands are tied.
Unless Xiaomi publish the source, we're not going to see a completely working custom kernel, if any at all.
Custom kernel would solve a lot of issues, we can also lower chipset voltage to save battery, increase performance, etc.
Even GPU OC might be possible if it is not fully locked. But that's just in the realm of good imagination at the moment.
In other terms, this is a bare kernel and it is also old leaked pre-release source, I believe full of bugs.
Any news about AOSP 5.1 ?