**** BEGIN LOGGING AT Sat Nov 13 02:59:57 2021 Nov 13 21:04:19 jonmason, ping Nov 13 21:08:51 ant__: yes? Nov 13 21:09:01 hello there Nov 13 21:09:30 hey Nov 13 21:09:48 I am being confused by the DEFAULTTUNE mismatch for 'recent' arm Nov 13 21:10:08 these are STB - set-top-boxes mostly broadcom and hisil Nov 13 21:10:54 now, I am hoping to match the reordering you've done, for next release Nov 13 21:11:11 https://forums.openpli.org/topic/86666-defaulttune-for-arm-devices/ Nov 13 21:11:37 ^ strangely no thumbs. is it normal wit these boards? Nov 13 21:12:36 after this, I went further: https://github.com/OpenPLi/openpli-oe-core/pull/1083 Nov 13 21:13:36 my first idea is that these manufacturer do not support actively (in general) so we have a kernel and a set of drivers, compiled with these older tunes Nov 13 21:14:17 changing it could be dangerous.... Nov 13 21:17:37 it seems DEFAULTTUNE = "cortexa15hf-neon-vfpv4" should catch almost all these boxes Nov 13 21:17:53 again, no thumbs? are maybe not implemented? Nov 13 21:21:07 sorry for the long Q, I am really confused and don't have any such device here... **** BEGIN LOGGING AT Sun Nov 14 06:02:15 2021 Nov 15 00:48:28 yes O4 does not make much sense infact that whole line maybe omitted. but -ffast-math is interesting, since user is saying I am fine with it and it will certainly force compiler to look for places to use more of neon instructions and thus perhaps improve performance for kodi, you should test it out Nov 15 00:49:26 if armv7vehf and cortexa15hf is the choice and you are looking for wider coverage for feeds then go with armv7vehf Nov 15 00:51:08 you can also use armv7vet2hf if you are interested in using better code compression but it will also mean more bugs even though using t2 is common over arm mode but still you will have a big change Nov 15 00:51:24 I would have used t2 from day 1 but it seems thats not the case for you **** ENDING LOGGING AT Mon Nov 15 02:59:57 2021