Hi Luiz,
On Wed, Mar 06, 2013, Luiz Augusto von Dentz wrote:
> int btd_profile_register(struct btd_profile *profile)
> {
> + int i;
> +
> + if (blacklist == NULL)
> + goto done;
> +
> + for (i = 0; blacklist[i]; i++) {
> + if (g_pattern_match_simple(blacklist[i], profile->name))
> + return -EPROTONOSUPPORT;
> +
> + if (profile->local_uuid != NULL && strcasecmp(blacklist[i],
> + profile->local_uuid) == 0)
> + return -EPROTONOSUPPORT;
> +
> + if (profile->remote_uuids == NULL)
> + continue;
> +
> + if (strcasecmp(blacklist[i], profile->remote_uuids[0]) == 0)
> + return -EPROTONOSUPPORT;
> + }
Since this is matching both local and remote UUID it seems like it
wouldn't be possible to just disable one role of an asymmetric profile
(like HFP) since no matter which role's UUID you give it'd always match
both roles.
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
