Re: Disable BlueZ profiles

Hi Kishore,

> Thanks for your reply....
> For IOPT testing SDP and L2CAP modules should be enough.
> My understanding is that for DUN/HFP/FAX the flow in the stack is
> something like the following:
> AT Commands--> RFCOMM-->L2CAP--> low level drivers
>
> And for the FTP and BIP profiles the flow is:
>
> OBEX--> RFCOMM-->L2CAP --> low level drivers
>
> So, in theory if RFCOMM and OBEX modules are removed from the linux
> kernel (Eg rmmod rfcomm), the DUN/HSP/FAX/FTP and BIP profiles  
> should be
> disabled.
>
> Similarly, removing bnep.ko from the kernel should disable PAN  
> profile.
> Is that a correct interpretation??
> Also, How do I use bluez-utils-3.32 to disable certain profiles?

the kernel only implements protocols and not profiles. And loading a  
module that implements a protocol doesn't mean that a profile becomes  
available. Also some protocols like OBEX, SDP and AVDTP are  
implemented in userspace.

The bluez-utils-3.32 has multiple options to handle these cases.  
Normally would not touch any of them and simply go ahead with the  
testing. They don't affect you. However if you do wanna change stuff  
look at the /etc/bluetooth/*.conf files (some of them might not be  
installed by default). So you have main.conf where you can disable  
certain plugins (plugins represent profile collections) and  
audio.conf, network.conf and input.conf. The bluez-utils source code  
contains example config for all plugins.

Regards

Marcel


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/