Hi Jan-Philipp, On Tue, Nov 3, 2020 at 4:43 AM Jan-Philipp Litza <janphilipp@xxxxxxxx> wrote: > > Pali Rohár wrote: > > Have I missed something? setsockopt() solution which I described in > > <20200419234937.4zozkqgpt557m3o6@pali> email is already runtime option. > > I think what Luiz meant was that there has to be a module option that > enables the additional kernel code, for example > > modprobe bluetooth enable_voice_setup=1 > > This would enable us interested folk to test the changes, while they > cannot blow up other peoples Bluetooth stack. At least that's the > reasoning that I assume. > > The setsockopt() is a runtime option on the application side but doesn't > "protect" the kernel. > > Content-wise, I understand Luiz' message as an approval of the general > API you proposed, as long as it is not active by default. Yes, in fact we are trending to introduce experimental interfaces for most of our new features so we can polish them and users can test with either build time option or runtime option like you mentioned above, this should balance the stabilization of new features with power users that do want to use them even though there are not marked as stable. -- Luiz Augusto von Dentz
