On 6/4/13 3:03 PM, Marcin Juszkiewicz wrote:
W dniu 04.06.2013 21:57, Andy Voltz pisze:
I just tried this solution with my vybrid cortex-a5 build. The only issue is a
parse error on ${CORTEX_ID} here:
TUNEVALID[cortex${CORTEX_ID}] = "Enable Cortex-${CORTEX_NAME} specific
I amended the changes so that each tune-cortexa5.inc (for example) looks like:
+CORTEX_ID = "a5"
+
+TUNEVALID[cortexa5] = "Enable Cortex-A5 specific processor optimizations"
+
+require conf/machine/include/tune-cortex.inc
I didn't think it was worth having a CORTEX_NAME if TUNEVALID does not parse..
Agree.
I had forgotten about this limitation. In a variable's [...] variable elements
are not extracted.
My only other thought is perhaps tune-cortex.inc should be called
tune-cortexa.inc? It seems like the m series is a different animal.
Agree as well. M/R to be exact.
What do you think?
This seems reasonable to me.
--Mark
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
