Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why GATT need full control of HCI device and how about BLE work before HCI_USER_CHANNEL #83

Open
Yushenbo opened this issue Oct 27, 2016 · 1 comment

Comments

@Yushenbo
Copy link

As you mentioned: We must need patch the HCI_USER_CHANNEL relevant commits, but how do kernel version before 3.13 support BLE?

@roylee17
Copy link
Contributor

You can use HCI_RAW_CHANNEL instead, but then you'll have two stacks manage the controller at the same time.

Kernel has link manager to manage links/connections. But BLE has been a moving target. Spec is evolving, and hardware vendors try to add new features/functions which was not standardized in spec. To keep up with the changes, BT stack in kernel is also evolving. Depends on which revision you're running, sometimes you have different behavior or different feature supported.

HCI_USER_CHANNEL allows us to have full and "exclusive" control of the controller in user space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants