On Wed, 2011-12-07 at 11:32 +0100, Dalleau, Frederic wrote: > A few weeks ago I've read about a policy module on that list. So far I've > seen any updates. I have nothing against handling the profile switch in > a separate module as long as it is done. This offers an additional > advantage : that could also be used to automate loading of module-loopback > for HFP HF role and A2DP sink role. Ok, great that we've reached agreement! Are there any volunteers for implementing module-bluetooth-policy? > > [1] I've actually already started to implement a shared "daemon proxy" > > It is likely that a big part of what you need is already > available in bluetooth-util.c. You just need to add a field to struct > pa_bluetooth_discovery with the adapters, and a hook to call > when an adapter is added (see found_adapter) and you're done. Yes, the bluetooth-util interface seems to be much closer to what I wanted to achieve with the daemon proxy than I first thought. It seems that I won't have any reason to keep the daemon proxy stuff separate from what already exists. I'll send an RFC patch that shows the bluetooth-util.h API of what I need (I haven't done much of the implementation yet). Please comment if you see something objectionable in it! -- Tanu
