Hi all, I've, like many, run into the issue of toolchain detection for the ti-sgx-ddk-km driver. I've noticed the ugly patch [1] getting edited to add new toolchains like arm-oe-linux-gnueabi and arm-poky-linux-gnueabi.
This is cumbersome because this step needs to be repeated for arbitrary toolchain vendors, and it is error-prone since the toolchain added doesn't explicitly mention the hardfp suffix expected by the driver, whereas arm-*-gnueabihf is already matched. My point is that I believe the proper fix for this is to make sure the toolchain generated by OpenEmbedded gets suffixed with "hf" when the hardfp tune is enabled, so that this ugly patch can be dropped and toolchain detection can work as expected. So far I've seen that the proper way to do this would be to set ABIEXTENSION .= "hf" accordingly given the arch tune. The only problem I've encountered so far is that the cross-canadian thingy [2] is zeroing the related variables for some reasons. Hence I'm not sure how to configure this properly. [1] http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch [2] http://cgit.openembedded.org/openembedded-core/tree/meta/classes/cross-canadian.bbclass#n64 Cc'ing Richard in case he has an input on the ugly ABI extension zeroing. Thanks, Vivien
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14053): https://lists.yoctoproject.org/g/meta-ti/message/14053 Mute This Topic: https://lists.yoctoproject.org/mt/86447553/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
