Dolphin, the GameCube and Wii emulator - Forums

Full Version: Is it possible to submit ucode to denver?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
wat.
If Google were trying to suck up to Qualcomm why would they invest in + release a product using hardware from their competitor in the first place?
(02-11-2015, 12:40 AM)tueidj Wrote: [ -> ]wat.
If Google were trying to suck up to Qualcomm why would they invest in + release a product using hardware from their competitor in the first place?

To "demonstrate" that alternatives aren't "better". Google uses the chipset,  only to gimp
It and make qualcomm look better.  They are trying to encourage devs to NOT give tegra any special attention, and to operate on baseline features.  Google literally has been limiting itself to the feature set qualcomm offers (case in the point the entire existence of the android extension pack).
I'm sorry but that's nonsense. They didn't build the fastest ARM android device currently on the market and make it their flagship product, with the newest release of their OS, just to "make qualcomm look better".
(02-11-2015, 12:50 AM)tueidj Wrote: [ -> ]I'm sorry but that's nonsense. They didn't build the fastest ARM android device currently on the market and make it their flagship product, with the newest release of their OS, just to "make qualcomm look better".

When you write it like that,  it makes me feel a whole lot stupider.  Maybe I'm getting a little over-zealous about this.  Still,  Google definitely needs to untangle their work here,  because the Nexus 9 from day one has had issues across the board.  Still not as baffling as mandatory encyption on new Armv7 devices like the nexus 6, causing insane eMMC lag and noticeable reductions in performance related to memory intensive tasks.
Not really surprising when apple is publishing short novels to advertise the fact that not even the feds can pull data from encrypted iDevices (spoiler alert: they can).
(02-11-2015, 01:58 AM)tueidj Wrote: [ -> ]Not really surprising when apple is publishing short novels to advertise the fact that not even the feds can pull data from encrypted iDevices (spoiler alert: they can).

Well Apple can get away with it thanks to Armv8 having AES instruction support,  meaning almost no overhead on memory tasks.  Same with the nexus 9,  which also avoids any noticable penalty.  Also,  i thought the feds were in a  fit because the encryption was actually working.  My issue is with using mandatory encryption on Armv7 exclusively.  I'm ok with the encryption on Armv8 devices,  where the benefits can exceed the rather limited trade offs.  But its been made clear that using encryption on Armv7 causes massive performance gulfs on memory.  Even Apple,  who so proudly touts their mandatory encryption,  doesn't actually enable it on Armv7 devices.  Google frankly should have used the same system,  because it really does cause a noticable difference in device behaviour.
Pages: 1 2