Re: Disable BlueZ profiles

Hi Marcel,

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?

Regards
Kishore.


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Marcel
Holtmann
Sent: Friday, May 30, 2008 2:15 AM
To: BlueZ users
Subject: Re: [Bluez-users] Disable BlueZ profiles

Hi Kishore,

> We found there are some unnecessary profile can be discovered when  
> doing Bluetooth Inter-Op Testing such as  DUN, FTP, FAX, PAN, BIP,  
> HFP. How can I remove/disable these profiles?
>
with bluez-utils-3.32 you have an option to disable certain profiles  
and only test some part. However having all profiles enabled should  
not be a problem at all. So what is your issue regarding inter-op  
testing?

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/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

-------------------------------------------------------------------------
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/