Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
03-20-2012 09:46 PM - edited 03-20-2012 09:48 PM
oops, I didn't notice this was in the NDK forum and assumed this was about Android player, please ignore.
Orignal post was:
Android NDK is not supported, so I assume ARM Neon is not either, unless you know a way to do that from Java/Dalvik...
03-20-2012 10:10 PM
Well the playbook uses an TI OMAP 4430 which is an implements a cortex a9 processor which implements armv7 ISA which should include neon extensions for the playbook. I am hoping that QNX neutrinos RTOS turns this functionality on as stated in this document
ARMv7 has two options for handling single-precision floating point: NEON and VFPv3.
ARMv7 processors boot with the NEON engine and Floating-Point Unit (FPU) disabled. Until you enable these features, attempting to execute any NEON or VFP instructions results in an undefined instruction exception.
At the time of release, the feature to generate NEON instructions wasn't tested on Cortex-A9 because there are currently no Cortex-A9 implementations with a NEON unit. As a result, the feature is available on an “as is” basis.
I am wondering if they defined these. I found the header for inline c of neon its called "arm_neon.h" I don't know how to get the compiler to compile it the ARM website said that its compiler dependent so how does QCC do this with momentics?
03-20-2012 10:44 PM
I think the document outlines how it works though its a long process I have to go through the conventions for makefiles and multiplatform build tree. To figure out how to tweek the build system ill probably write a tutorial for it sooner or later =)