I'm trying to achieve in bluetooth a way to bypass the HCI. I'll elaborate. in the HCI H4 layer there is the event field. I want to be able to send HCI Commands. now - if i'll do it currently - the commands will stop at the controller as it recieved a command . What I want to achieve with my two BT modules (BR/EDR) - Is to send an HCI H4 event to another BT Module. for example - "Change local name" command.
So - again - my end goal is to send an HCI event through the controller to another one, without the need to "reverse engineer" the bluetooth firmware to add hooks/changes.
You can think of it like I just want my HCI to serve as "proxy" to send my own defined packets straight to another controller without any intervention.
You can look at the answer here: how event packet header is getiing in hci_send_req api implementation?
I want to be able to make my controller send my own HCI H4 Packet indicator. (for example: 0x01 - command packet)
Thanks Jen.