Basic Bluetooth coding questions relations and terminology in Linux kernel
by jan128 from LinuxQuestions.org on (#5AX56)
I am working on solving an annoying Bluetooth issue in Linux / blueZ stack.
To solve that I am trying to understand "who is on first" in bluetooth coding hierarchy and terminology as far as Linux kernel goes.
I am using QtCreator IDE which has "Bluetooth module".
I am guessing this Qt term "module" is "top layer" encapsulating "blueZ stack" and it works as expected - with one exemption - once the "nearby Bluetooth device" is detected it will continue to be detected even when physically removed form the system.
I am used to "source code" linked to "library" terminology.
My question is
is Qt module similar to C library as far as relations goes?
Hence I have
my source code
bluetooth module
blueZ stack / library
Second question
how does "HCI" (?) relates to "blueZ stack "?
Is this correct?
Linux kernel
blueZ stack - high level code
HCI human computer interface (?) - "assembly code " ?
I like to have reply correcting my terminology and or validity of the relations concept.
I am not sure how "driver" fits into scheme, but for now I am primarily interested in basic terminology. Hardware questions will come later.
To solve that I am trying to understand "who is on first" in bluetooth coding hierarchy and terminology as far as Linux kernel goes.
I am using QtCreator IDE which has "Bluetooth module".
I am guessing this Qt term "module" is "top layer" encapsulating "blueZ stack" and it works as expected - with one exemption - once the "nearby Bluetooth device" is detected it will continue to be detected even when physically removed form the system.
I am used to "source code" linked to "library" terminology.
My question is
is Qt module similar to C library as far as relations goes?
Hence I have
my source code
bluetooth module
blueZ stack / library
Second question
how does "HCI" (?) relates to "blueZ stack "?
Is this correct?
Linux kernel
blueZ stack - high level code
HCI human computer interface (?) - "assembly code " ?
I like to have reply correcting my terminology and or validity of the relations concept.
I am not sure how "driver" fits into scheme, but for now I am primarily interested in basic terminology. Hardware questions will come later.