Hi,=0A=0AIn certain cases, as in using VS commads to communicate with diffe=
rent cores on the combo chips (say, BT, FM, GPS) - we would have to use the=
hci0 interface without it being UP.=0A=0AAs in the hci0 interface still ne=
eds to be invisible (via dbus/bluetoothd) to the system but to be available=
to be use.=0A=0AIs there a way we can do this while registering with the h=
ci ?=0Asay a flag in the struct hci_dev to be by default during registratio=
n HCI_DEV_DOWN to be default state ?=0A=0A
Hi Pavan,
> In certain cases, as in using VS commads to communicate with different cores on the combo chips (say, BT, FM, GPS) - we would have to use the hci0 interface without it being UP.
>
> As in the hci0 interface still needs to be invisible (via dbus/bluetoothd) to the system but to be available to be use.
>
> Is there a way we can do this while registering with the hci ?
> say a flag in the struct hci_dev to be by default during registration HCI_DEV_DOWN to be default state ?
it is a pretty simple fact that the HCI device has to up. Otherwise it
is not going to work. Same with an Ethernet interface. That is the
proper state for such interfaces.
What you want is to set RAW mode on the HCI device before bringing it
up. Then bluetoothd will actually ignore it.
However I am not sure what you are really trying to achieve here since
every device will be brought up automatically by bluetoothd. And so you
are already to late to the game at that point.
Regards
Marcel