Re: Bluetooth 5 support - configurability

Hi, On Monday, 10 April 2017 22:42:53 CEST will sanfilippo wrote: > +1 on opt-in for BT5 although I do think there are quite a few configuration > variables for features that are on by default. Not sure there is a rhyme or > reason, other than possibly the thought that “most people would be

Re: Bluetooth 5 support - configurability

+1 on opt-in for BT5 although I do think there are quite a few configuration variables for features that are on by default. Not sure there is a rhyme or reason, other than possibly the thought that “most people would be enabling this, so let’s have it on by default”. > On Apr 10, 2017, at

Re: Bluetooth 5 support - configurability

Hi, On 10 April 2017 at 18:15, will sanfilippo wrote: > I think #3 is fine as well. If, for some reason, folks do not want to > claim 5.0 support they can always use release 1.0.0 of Mynewt. > > > > On Apr 10, 2017, at 6:16 AM, Szymon Janc wrote: > >

Re: Bluetooth 5 support - configurability

I think #3 is fine as well. If, for some reason, folks do not want to claim 5.0 support they can always use release 1.0.0 of Mynewt. > On Apr 10, 2017, at 6:16 AM, Szymon Janc wrote: > > Hello Community, > > We are currently upstreaming Bluetooth 5 functionality into

Bluetooth 5 support - configurability

Hello Community, We are currently upstreaming Bluetooth 5 functionality into Apache Mynewt. Sine all of the new features are optional to support (excluding internal dependencies) we could make Mynewt code configurable per feature. It shouldn't be too much hasle to support this via syscfg.yml