It's known that both S7/E variants are shipping with Vulkan support out of the box, I'm trying to find driver version of Snapdragon variant. Recently I discovered Exynos variant of Vulkan driver developed by ARM (thanks to one of the reddit members). it'll be great to see Qualcomm's driver version, what features it has and compare them directly. To find out driver version you'll need to install an app (profilers like AIDA64 or Antutu won't be able to expose Vulkan extensions) VulkanCapsViewer : http://vulkan.gpuinfo.org/download.php , run it then submit a log (app should create one automatically) onto their database, so we get all the features exposed just like here (Exynos 8890 comparison to Tegra K1 Vulkan drivers): http://vulkan.gpuinfo.org/compare.php?compare=compare&id[128]=on&id[78]=on
I guess it's pretty simple to do for someone, just like running a benchmark
Solved
Anyone interested could check their database as log was submitted
Related
Hi!
I've been trying to find any documentation on Snapdragon's DSP and hardware based video and audio decoders. So far, nothing. I'm just thinking if it would be possible to cook the support into custom ROM as it is quite ridiculous that decoding something like MP3 or AAC takes any CPU time at all, as according to Qualcomm's web site Snapdragon has hardware support for decoding MP3, AAC and H.264. I take it Qualcomm only provides the documentation to partners, as it is impossible to find?
Hopefully full support for hardware acceleration comes with WM7, if it can not implemented on 6.5. Should be doable with custom driver (in kernel mode) anyway by cooking, provided the documentation is leaked or something.
Mikko.
It's not possible to have the SnapDragon documentation because Qualcomm will never release it.
It's possible instead to have the missing SnapDragon drivers for Linux or I hope for Windows CE only when a QSD based smartbook that will have these drivers will be out.
With Windows Mobile 7 it's a whole new story, new CE7 kernel and support for all the new ARM instructions. I hope that we'll get that things and soon
kholk said:
It's not possible to have the SnapDragon documentation because Qualcomm will never release it.
It's possible instead to have the missing SnapDragon drivers for Linux or I hope for Windows CE only when a QSD based smartbook that will have these drivers will be out.
With Windows Mobile 7 it's a whole new story, new CE7 kernel and support for all the new ARM instructions. I hope that we'll get that things and soon
Click to expand...
Click to collapse
That's a waste of potential, but we can only wait (or not? )
you Cant really expect qualcomm to release documents on its IP.
but it would be nice if they and htc worked together to release a dev sdk.
if they are serious about developing the platform then its a step they really do need to make.
if samsung can get a sdk out for the omnia ii then it seems sensible to think htc need to play catchup.. the chipset does have potential,and it appears qualcomm are becoming more dev friendly.
look at what southend have achieved with some decent support from QC..
documentation?
Qualcomm should be giving documentation to ISVs its just a matter of it falling in the wrong(or right) hands. In the meantime, Snapdragon uses ARM Cortex-A9 core and you can find more details here:
http://www.arm.com/products/CPUs/ARMCortex-A9_MPCore.html
Not sure if that includes DSP.
My acer s200 has support for H.263, H.264 out the box =]
Ca5c4d3 said:
Qualcomm should be giving documentation to ISVs its just a matter of it falling in the wrong(or right) hands. In the meantime, Snapdragon uses ARM Cortex-A9 core and you can find more details here:
http://www.arm.com/products/CPUs/ARMCortex-A9_MPCore.html
Not sure if that includes DSP.
Click to expand...
Click to collapse
Snapdragon is Cortex A8 based and yes it does have DSP
mightymn said:
Snapdragon is Cortex A8 based and yes it does have DSP
Click to expand...
Click to collapse
Do you know are the hardware multimedia decoders really silicon or SIMD/DSP based? From the QC's documentation you get the feeling they are ASIC stuff, but it might be marketing and in reality they are IP cores.
Mikko.
mikolas said:
Do you know are the hardware multimedia decoders really silicon or SIMD/DSP based? From the QC's documentation you get the feeling they are ASIC stuff, but it might be marketing and in reality they are IP cores.
Mikko.
Click to expand...
Click to collapse
Nope, don't know that
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.
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
If Vulkan API is implemented at our phone it would be fantastic. Hope Asus will work on the API and make the best for our phone, let's see in a couple of months of so
Too good to be true man, too good to be true.
hi, I'm very interested in everything about vulkan since i could see some videos about it. But my knowledge about api, android and rom's is not that good, so i would thank you if i could get some answers.
1 - Is this implementation of API a work for ASUS or Intel?
2 - Since i saw that PowerVR Rogue has now SDK(i dont know what it is) for Vulkan, Is ANYONE able to make a custom rom that could use Vulkan?
3 - I've heard that Android N will have native support for Vulkan. Does it mean that if i download a custom rom, like a cyanogenmod, for Android N to my Zenfone 2 i will have the benefits of using Vulkan?
4 - Does anyone know if that Galasy S7 that had 135k+ on antutu was using Vulkan? Because my Zenfone 2 is a great phone and only scores 65k, it's scary to thing that a S7 should have more than the double of hardware capacity that my Zenfone has. I thing that should be because of vulkan, but i need to hear it from someone who knows what's talking.
I hope to get answers for this questions. Thank you all.
SSJMatt said:
)Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
Click to expand...
Click to collapse
Sorry, that's not how ASUS usually manages fixes and updates. That would take time and money and we've already spent our money so they have nothing to gain, therefore nothing will happen. Only future customers are a priority for ASUS.
A happy ASUS customer is one with low expectations.
Well, at least It'd give Asus a good excuse for being so late...
Vulkan is something that would need to be implemented at the OS level on Android (mainly the kernel, no idea what other bits Google is including in the rest of the OS). And support for each hardware would need to be provided by the OEM or manufacturers. It MAY be possible for a custom ROM to implement Vulkan support in some fashion in a current version of Android (harder and more "impossible" things have been accomplished) but it's not likely due to too many technical challenges. Besides, it wouldn't happen until after Android N is released and the AOSP code is posted. Only then would someone attempt to backport Vulkan.
I'm not 100% sure, but I do believe that Vulkan support will be a requirement by Google for devices to run Android N. So if Asus does plan on upgrading the phones then they will need to include a kernel for the hardware that supports Vulkan and those drivers would come from Intel. So the chance of the Zenfone supporting Vulkan is 100%, provided Asus upgrades it to N.
SSJMatt said:
I just heard that Vulkan API is coming to mobile and it is supporting PowerVR chips like the one we have on the phone.
(PowerVR G6430). Some people say on the ZENTALK forum that that's why it takes so much freaking time for Asus to implement Marshmallow as they are busy incorporating the API on the phone.
If this is true just image the gigantic boost it will give to our phones! (just watch on Youtube or search on Google for more information about Vulkan API)
Click to expand...
Click to collapse
So is the VULCAN API present in the M update?
Is Vulkan something like the Mantle for Desktops?
EDIT:
Vulkan Drivers for Nexus Player
Google’s Android Image
As part of the Android N Developer Preview 2 release, Google released an Android N image for the Nexus Player that includes Vulkan drivers. You can find out more about the Android N Developer Preview here and can download the image here. As this image is officially supported by Google, we recommend using it for Vulkan Android development.
Click to expand...
Click to collapse
https://community.imgtec.com/developers/powervr/vulkan/
There is two possibilities:
1- Vulkan added in Android N's mainline code, and CM14 (maybe) will do this too.
2- Vulkan driver will be only in manufacters Android N's source. In this case, will be needed to be backported.
In both possibilites, isnt impossible to do it, even without Asus help. But would be awesome if some official MM give it to us (not in the first version, obviously).
Its GPU manufacturer job to implement vulkan, they provide the drivers to OEM manufacturer implement it on their otas. Nvidia already did that on latest MM update to shield TV and shield tablet.
As the title says Vulkan is not working on the TMO version of the LG V20. I tried all the games that currently support Vulkan and they all say device not supported (some games just won't use the highest graphics settings). After hours searching for a reason why, I can only find articles about the S7 and S7E supporting Vulkan. I ran AIDA64 and it shows that the files/extensions are on the phone. Any one have any ideas as to why an Android N device with the required hardware/extensions is not making use of Vulkan? Is LG to blame?
Hello,
Is the nexus 6p compatible with galileu gps system?
Or is it possible that in a near future becames compatible?
According to Qualcomm, SnapDragon 810 is not compatible, while 2016 processors (820/821 ...) it is.
brandaopj said:
Hello,
Is the nexus 6p compatible with galileu gps system?
Or is it possible that in a near future becames compatible?
Click to expand...
Click to collapse
lordemines said:
According to Qualcomm, SnapDragon 810 is not compatible, while 2016 processors (820/821 ...) it is.
Click to expand...
Click to collapse
I'm a little bit confused, because I've read this on another website:
According to Qualcomms website the Snapdragon 810 (like in my Nexus 6P) should support Galileo. But no doubt they'll refuse to release the necessary driver or code so people have to upgrade to a newer phone if they want it.
https://www.qualcomm.com/news/relea...cessor-powers-premium-tier-mobile-experiences​
Galileo and Gps uses the same frequency for L1 band so on hardware side it should be OK. Now for the proprietary drivers is another story..
Are there other receivers already giving good positionning? Last time I check there weren't all spacracfts launched ? They had stability problems on their clocks.
Are they any news on snapdragon 810 support for galileo? It will be possible to make it work? too bad that Qualcomm says first it supports galileo and then only new processors will support it.
If there is not a problem with hardware I am pretty sure someone can force them as they advertise 810 as galileo supported. Usually what you advertise you must bring to buyers.