On Thu, 2019-10-17 at 15:34 +0200, Hyperion wrote:
> Regression would mean that some devices can't connect anymore : this
> won't happen if a workaround is provided, and this workaround won't
> be used often.
>
> Most (99% ?) of the devices will work correctly with my patch (many
> of them in XQ m
That's Why I proposed to set the config switch to "legacy max negotiated bitpool" (current code) by default, and let the user decide if he/she wants to activate the "XQ max negociated bitpool" (my patch). This way it's less likely to cause regressions than Pali's "forced bitpool" XQ modes : by def
Yes !!! for the module argument ! (just a boolean is needed). Which module ? (module-bluez5-device ?). JP 18.10.2019, 14:52, "Hyperion" :That's Why I proposed to set the config switch to "legacy max negotiated bitpool" (current code) by default, and let the user decide if he/she wants to activate
