[OE-core] [PATCH] connman: tist of connman do not support powerpc64

Koen Kooi koen at dominion.thruhere.net
Fri Apr 26 10:21:03 UTC 2013


Op 26 apr. 2013, om 11:33 heeft Jack Mitchell <ml at communistcode.co.uk> het volgende geschreven:

> On 26/04/13 09:07, Chunrong Guo wrote:
>>     connman build for powerpc 64bit boards were producing errors like this:
>>     | make[1]: *** [plugins/plugins_tist_la-tist.lo] Error 1
>>     | make[1]: *** Waiting for unfinished jobs....
>>     | make: *** [all] Error 2
>>     | ERROR: oe_runmake failed
>> 
>> Signed-off-by: Chunrong Guo <B40290 at freescale.com>
>> ---
>>  meta/recipes-connectivity/connman/connman.inc |    3 ++-
>>  1 files changed, 2 insertions(+), 1 deletions(-)
>> 
>> diff --git a/meta/recipes-connectivity/connman/connman.inc b/meta/recipes-connectivity/connman/connman.inc
>> index 589ece8..5389f3a 100644
>> --- a/meta/recipes-connectivity/connman/connman.inc
>> +++ b/meta/recipes-connectivity/connman/connman.inc
>> @@ -20,10 +20,11 @@ DEPENDS  = "dbus glib-2.0 ppp iptables gnutls \
>>              ${@base_contains('DISTRO_FEATURES', '3g','ofono', '', d)} \
>>              "
>>  -INC_PR = "r19"
>> +INC_PR = "r20"
>>    TIST = "--enable-tist"
>>  TIST_powerpc = ""
>> +TIST_powerpc64 = ""
>>    EXTRA_OECONF += "\
>>      ac_cv_path_WPASUPPLICANT=${sbindir}/wpa_supplicant \
> 
> Is there a reason that we need to specifically enable TIST at all? This is quoted from one of the developers on the ConnMan list:
> 
>> it is special hardware where we need this plugin for. As I said, I was considering to remove the plugin actually. So it is safe to > disable this plugin.
> 
>> By default this plugin is actually disabled. And we do not even build test it for the releases.
> 
> I think if anyone needs it, shout up; otherwise we should go with the default and disable it.

What's it actually doing? Kernel loads wifi firmware, you can use hciattach manually or uim automatically to enable bluetooth on wl1xxx chips, which are the only users of the TI shared transmission stuff. As far as I'm concerned it can be globally disabled :)



More information about the Openembedded-core mailing list