Hi Andre, > This patch adds a new command to management interface to enable/ > disable LE support. This command will be used to set LE support > according to the host configuration. any reason why we want this separated and being under host stack control in the first place. Should we not always enable LE if we can support it? What are the reason to run an LE capable BlueZ on an LE capable dongle and then not enable LE? A similar argumentation applies for Secure Simple Pairing. We are currently enabling this by default. Even while there are qualification tests that would us force to run it with SSP disabled. Maybe we should just have a generic kernel mgmt features enabling command. One thing that I do not wanna do is to just blindly make a copy of HCI commands for mgmt interface. The controller abstraction for the mgmt interface is suppose to have a feature list so we can check what the kernel supports and what not. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
