Add bthfp device config. #94
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Even though not currently used with bluez4, add bthfp device configurations to the xpolicy.conf already. With bluez5 policy configuration the old bthsp device is split to bthsp and bthfp, to manage the two profiles easier. Old implementation only had hwid property with bthsp device which contained the info about which bluetooth profile was in use. When the two profiles have own devices in policy configuration managing the routing is much simpler.
|
Closing the PR as it is obsolete by now. Card configurations are split in bluez4.conf and bluez5.conf and common device configs are in xpolicy.conf |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even though not currently used with bluez4, add bthfp device
configurations to the xpolicy.conf already.
With bluez5 policy configuration the old bthsp device is split to bthsp
and bthfp, to manage the two profiles easier. Old implementation only
had hwid property with bthsp device which contained the info about which
bluetooth profile was in use. When the two profiles have own devices in
policy configuration managing the routing is much simpler.