Hi,
does anyone know how the arm trustzone extension is implemented in snapdragon s4?
I am developing on google nexus 4 phone, which uses snapdragon s4 pro. in the kernel provided by google's AOSP, the platform dependant code (/kernel-msm/arch/arm/mach-msm) uses secure monitor call (smc) to enter the secure world. I wonder how this secure world is implemented for snapdragon s4. Is this part open sourced? where can I find the source code and are there any documentation for that?
Is there a way to disable trust zone on nexus 4?
Thanks
Related
http://www.phoronix.com/scan.php?page=news_item&px=MTIxMjU
Samsung Set To Open-Source Parts Of The Exynos
Posted by Michael Larabel on October 22, 2012
It appears that Samsung is preparing to open-source some code pertaining to their Exynos ARM SoC.
At an event this weekend (YouTube stream), Samsung said they will open-source the kernel and platform components of their Exynos SoC. This new code is said to be dual-licensed under the GPLv2 and Apache 2.0 licenses.
Samsung also says it will support ARM Mali GPU driver development, which it uses with its Exynos SoC. It's not known at the moment whether this means supporting the community Lima driver project or something else.
As part of this new open-source initiative, Samsung looks like it will be upping its Linux support for the Origenboard, its primary Exynos development board.
Up to this point for Exynos there's been bits of open-source drivers, like their Exynos DRM driver that is in the mainline Linux kernel but the 3D bits are not covered and they have no open-source user-space for 3D / OpenGL ES coverage.
It will be interesting to see what Samsung ultimately does with their Exynos open-source play since most ARM SoC vendors aren't too open-source friendly up to this point. It was just days ago though that word on the new Google Chromebook emerged, which boasts a Samsung Exynos 5250 SoC with Cortex-A15 cores.
Google certainly does like open-source for their ChromeOS work such as their work on Coreboot support for new hardware and Google's work on open-source graphics drivers for use by their earlier Intel-based Chromebooks.
Click to expand...
Click to collapse
We'll see how this plays out. It's not the first time Samsung promised us something.
BatGnat said:
http://www.phoronix.com/scan.php?page=news_item&px=MTIxMjU
Click to expand...
Click to collapse
Hi, this is already being discussed in this thread http://forum.xda-developers.com/showthread.php?t=1925709 . No point posting it twice. Things are not what they seem apparently. Read Entropy512's post on the thread I linked for more information on that.
Yesterday was the day the Google Play editions of the HTC One and the Galaxy S4 were unleashed to the Playstore.
This may be a bigger deal than most of us give credit to.
It could be the start of Google taking more control over Android back to themselves.
But... Those OEMS still optimize the Kernel to work with their respective Chipsets/Camera's and other hardware features.
Wich means the code will be optimized for example the Exynos Processor inside the Galaxy S4.
My question is: Can we eat the fruits of this mighty fine tree?
Could it be possible to use some of this code to transform it into something usable for good old GT-I9100?
I know it's probably wishful thinking, but nonetheless; One can dream RIGHT??
We would need an S2 google edition.
Sent from my GT-I9100 using xda app-developers app
Well no, the google edition is the Snapdragon version.. not the exynos version..
That sounded (sadly enough) completely logical, thanks.
If only Samsung opened up a bit. There is little for Sammy to loose if they gave 'old' S2 the hackers delight treatment.
That s4 has snapdragon s600. No luck for exynos source codes.
What we should take from this is: do not get anything with "own" components, get something with commonly used components. It will be rather easy to port stuff for such architecture (Qualcomm chipsets for example).
kokesh said:
What we should take from this is: do not get anything with "own" components, get something with commonly used components. It will be rather easy to port stuff for such architecture (Qualcomm chipsets for example).
Click to expand...
Click to collapse
Yes, even if that means you are not getting the best hardware...sadly enough that is true
I was sooo hoping samsung would start caring, and just did the popular thing to do.
fejth said:
Yesterday was the day the Google Play editions of the HTC One and the Galaxy S4 were unleashed to the Playstore.
This may be a bigger deal than most of us give credit to.
It could be the start of Google taking more control over Android back to themselves.
But... Those OEMS still optimize the Kernel to work with their respective Chipsets/Camera's and other hardware features.
Wich means the code will be optimized for example the Exynos Processor inside the Galaxy S4.
My question is: Can we eat the fruits of this mighty fine tree?
Could it be possible to use some of this code to transform it into something usable for good old GT-I9100?
I know it's probably wishful thinking, but nonetheless; One can dream RIGHT??
Click to expand...
Click to collapse
think google edition doesnt use exynos chipset
both use the qualcom snapdragon 600
I'm a long-time Omni user on my Nexus devices. My wife recently got a Samsung Galaxy Note 10.1 2014 Edition (LTE) as part of her contract, and I cannot begin to explain how frustrating it is to be back in "Samsung's world". The hardware is incredible (Snapgragon 800, 3GB RAM, 2560x1600 display) but it is loaded with bloat on an outdated 4.3 ROM (only the wifi-only model (Samsung Octa) has Kitkat so far).
Now I know that for a device to be supported, it needs a maintainer. This is a very expensive, niche device, and I presume that there are not many users out there that will be suitable. So my question is, what does the job of a maintainer entail exactly? I've built CM for a couple of devices from source before, but that's about the extent of my knowledge with regards to custom ROM development. Is that sufficient?
I'm thinking that this device should be a fairly easy bring-up, being based on the same SOC as the Nexus 5 (amongst others).
How can I make this happen?
StNickZA said:
I'm a long-time Omni user on my Nexus devices. My wife recently got a Samsung Galaxy Note 10.1 2014 Edition (LTE) as part of her contract, and I cannot begin to explain how frustrating it is to be back in "Samsung's world". The hardware is incredible (Snapgragon 800, 3GB RAM, 2560x1600 display) but it is loaded with bloat on an outdated 4.3 ROM (only the wifi-only model (Samsung Octa) has Kitkat so far).
Now I know that for a device to be supported, it needs a maintainer. This is a very expensive, niche device, and I presume that there are not many users out there that will be suitable. So my question is, what does the job of a maintainer entail exactly? I've built CM for a couple of devices from source before, but that's about the extent of my knowledge with regards to custom ROM development. Is that sufficient?
I'm thinking that this device should be a fairly easy bring-up, being based on the same SOC as the Nexus 5 (amongst others).
How can I make this happen?
Click to expand...
Click to collapse
Being a maintainer takes a LOT of reverse engineering skills. Integrating the OEM's blobs with "normal" AOSP or CAF sources can be a royal pain.
The best bet is to try and start your bringup by using a similar device as a starting point. Same platform is OK, same platform AND OEM is better.
For example, all of the Exynos 4210 devices (except the Tab 7 Plus/7.7) share a common device tree and kernel nowadays (the 7Plus/7.7 were too different from others in the family)
All of the Exynos 4412 devices have a common device tree that's inherited, and a common kernel.
Unfortunately, unlike the Note and Note 2, the Note 3 is significantly different from the GS4. However, your device might be similar to a Note 3, so you MIGHT be able to get started by adding Note 10.1 2014-specific parts to the Note3 kernel and modifying the device tree in a similar fashion.
The best way to learn maintainer skills is to find a device that is semi-supported and start working on figuring out how to fix its features that aren't quite working right. (In my case, I worked with atinm on resolving I777-specific issues to get that device lit up, then started working on remaining I9100/I777-common issues in CM back in the ICS days, then started on the Note which was similar to I777/I9100)
Expect to spend a LOT of time Googling stuff and searching through code. "grep", "strings" and "readelf -d" are your friends. (grep is for searching anything, strings is for looking at the strings in a blob, readelf -d shows you what libraries a blob depends on)
Even an experienced maintainer spends ****-tons of time searching for things and digging through data.
Patience is the most critical thing for a maintainer to have.
Entropy512 said:
Being a maintainer takes a LOT of reverse engineering skills. Integrating the OEM's blobs with "normal" AOSP or CAF sources can be a royal pain.
The best bet is to try and start your bringup by using a similar device as a starting point. Same platform is OK, same platform AND OEM is better.
For example, all of the Exynos 4210 devices (except the Tab 7 Plus/7.7) share a common device tree and kernel nowadays (the 7Plus/7.7 were too different from others in the family)
All of the Exynos 4412 devices have a common device tree that's inherited, and a common kernel.
Unfortunately, unlike the Note and Note 2, the Note 3 is significantly different from the GS4. However, your device might be similar to a Note 3, so you MIGHT be able to get started by adding Note 10.1 2014-specific parts to the Note3 kernel and modifying the device tree in a similar fashion.
The best way to learn maintainer skills is to find a device that is semi-supported and start working on figuring out how to fix its features that aren't quite working right. (In my case, I worked with atinm on resolving I777-specific issues to get that device lit up, then started working on remaining I9100/I777-common issues in CM back in the ICS days, then started on the Note which was similar to I777/I9100)
Expect to spend a LOT of time Googling stuff and searching through code. "grep", "strings" and "readelf -d" are your friends. (grep is for searching anything, strings is for looking at the strings in a blob, readelf -d shows you what libraries a blob depends on)
Even an experienced maintainer spends ****-tons of time searching for things and digging through data.
Patience is the most critical thing for a maintainer to have.
Click to expand...
Click to collapse
Thanks Entropy. Sounds like I don't have what's required for the job.
Entropy512 said:
However, your device might be similar to a Note 3, so you MIGHT be able to get started by adding Note 10.1 2014-specific parts to the Note3 kernel and modifying the device tree in a similar fashion.
Click to expand...
Click to collapse
The Note III (LTE) is the N9005, and I think the device code is hlte. I can't find a version of Omni for this device either.
StNickZA said:
The Note III (LTE) is the N9005, and I think the device code is hlte. I can't find a version of Omni for this device either.
Click to expand...
Click to collapse
Yeah, no one has done an Omni bringup yet. IbrahimA was considering doing one based on the CM bringup but he hasn't had the time.
Firstly, I'm NOT a Developer - I want to make that very clear
I have been trying to get data/info about what ever happened to the Original Samsung Galaxy S4 'TouchWiz'
Camera feature/ability to be able to 'Simultaneously' record videos (not talking about taking pictures here)
with both the front and back cameras on the phone.
This question has been asked before by a very very very small number of people on the net including in XDA
developers forums, However these questions only have been asked on forums relating to NEXUS phones/devices.
When i originally bought my S4 (second hand) i used the recording feature, i absolutely love it, i think it it brilliant,
it is one of the reasons why the S4 has such appeal for me.
I later upgraded to CyanogenMod, because of privacy concerns relating to Samsungs Involvement with the NSA over
their KNOX security.
The OS seemed fine to me, but this security concern was the basis of WHY i moved over to CyanogenMod.
Then i found out, that CyanogenMod does NOT Support the Dual Camera feature.
I contacted Samsung, and they told me that the Camera app was not really an app at all, but was in fact part of the OS itself.
But remember, the Genuine Samsung Galaxy is actually model number GT-i9500, which uses the Exynos Chip, unlike the Samsung Galaxy S4
variant known as the S4 LTE GT-i9505, which uses the Qualcom Chipset.
It has also been said by some XDA developers, that Samsungs 'TouchWiz' is not Open Source, it is Closed Source.
Well belonging to the company, this is no surprise, I'll also bet that it is probably Patented as well.
I say, so what ?, CyanogenMod does NOT need the original samsung 'TouchWiz' code, it only needs to know the HardwareSpecs of the Qualcom
Chip, then programming/developing can begin.
The S4 is already Superceeded by the S5 (and any possible variant(s) of that), i feel that the GT-i9505 is getting left out of the picture.
Are there any answers to this mystery ???
Just found out that other Exynos (5420) devices already have working non-samsung roms (i.e. CM11 & MIUI)... makes me wonder what do they have that we don't?
Source code should be (almost) identical, shouldn't it?
(I know that developement / porting is hard work & I'm certainly not "demanding" anything [that would be quite disrespectful] :angel:... I was just wondering, because up to this point the main argument for why there are no CM / AOSP roms has been the lack of source code for the Exynos SoC)
Cyanogenmod 11.0:
SM-T520 Tab Pro 10.1 WiFi
SM-T700 Tab S
MIUI:
N9000 Note III Exynos
I would also like to know and mantain this post as an informative post and not as a demand or petition; I am just really curious as to what makes our tab so special and if anything can be done about it. Hell, i would even like to try to do it myself but i got no time until winter vacations and i am not sure if this tab is something a begginer like me can start with.
The Arndale Octa (Exynos5420) board also has an AOSP build so there’s probably source lying around in either Linaro’s or Insignal’s git repos (or both).
EDIT:
http://git.insignal.co.kr/
EDIT 2:
https://android.git.linaro.org/gitweb/device/linaro/arndale_octa.git