On 04.02.2017 19:29, Alexander E. Patrakov wrote:
The choice of the option name is unfortunate. Imagine if another
situation appears where we would either use or not use getsockopt() to
get some other parameter. How about renaming it to something like
autodetect_mtu?
Yes, sounds much better. I'
The choice of the option name is unfortunate. Imagine if another
situation appears where we would either use or not use getsockopt() to
get some other parameter. How about renaming it to something like
autodetect_mtu?
2017-02-04 23:13 GMT+05:00 Georg Chini :
> A recent patch changed the MTU size f
A recent patch changed the MTU size from the default value of 48 to the value
returned by getsockopt(). This breaks HSP for some setups. To circumvent the
problem, this patch introduces a boolean parameter "use_getsockopt" for
module-bluetooth-discover, module-bluez5-discover and module-bluez5-devi