- Oct 05, 2010
-
-
Marcel Holtmann authored
-
Marcel Holtmann authored
-
Marcel Holtmann authored
-
Suraj Sumangala authored
This patch add support for specifying patch download address for AR300x patch download logic.
-
Vinicius Costa Gomes authored
When a pincode was entered and no DBus error ocurred, bluetoothd still responded with Pin Code Request Negative Reply. The regression was introduced by commit e7daece8
-
- Oct 04, 2010
-
-
Claudio Takahasi authored
-
Claudio Takahasi authored
Fix interleave discovery type verification. This patch fix the wrong scanning request for LE only devices. When the adapter state changes to idle, the next scanning window for LE only should be triggered by the scheduler.
-
Claudio Takahasi authored
Periodic inquiry doesn't send an event between inquiry windows. If devices are not found during the inquiry session or if the state is resolving name periodic inquiry still active and needs be deactivated.
-
Claudio Takahasi authored
For standard or periodic inquiry the scheduler can start a new discovery session before the name resolution procedure has finished. For this case a dupplicated Discovering=TRUE signal shall not be sent.
-
Claudio Takahasi authored
This patch add a new function in order to have a clear separation between state and the requested discover type based on the host/ controller capabilities. "state" shall be exclusive, except for the suspend that it is necessary to know the previous state.
-
Claudio Takahasi authored
If the procedure to resolve remote device names takes more than the DiscoverSchedulerInterval a new discovery "session" could start interfering the current state. Postpone discovery logic is simpler than cancel the pending operations and send all required D-Bus signals.
-
Claudio Takahasi authored
-
Claudio Takahasi authored
Discovering=TRUE/FALSE property is not being sent to indicate when a new periodic inquiry window starts/ends.
-
Claudio Takahasi authored
-
Claudio Takahasi authored
-
Claudio Takahasi authored
External applications can trigger inquiry, for this case interleave is not applicable.
-
Claudio Takahasi authored
With dual mode adapters, "discovery" expression is being used to represent both BR/EDR inquiry and LE scanning.
-
Claudio Takahasi authored
-
Claudio Takahasi authored
Local extended features page 1 is required to check if the host supports LE. Bit 1 one the byte 0: LE Supported(Host) needs be set on LE capable adapters.
-
Claudio Takahasi authored
-
Claudio Takahasi authored
For BlueZ if the controller supports LE, extended feature mask shall be set to indicate that the host supports LE and disable simultaneous LE and BR/EDR for simplicity even if the controller supports simultaneous LE and BR/EDR.
-
Claudio Takahasi authored
Remote name discovery shall be executed after the interleave discovery for dual mode adapters or after the inquiry complete for BR/EDR only.
-
Claudio Takahasi authored
For interleave discovery, inquiry length parameter can be used to finish the inquiry procedure instead of send a inquiry cancel command.
-
Claudio Takahasi authored
For BR/EDR only adapters, the recommended inquiry length is 0x08 (10.24 seconds). For interleave discovery the inquiry length is 0x04(5.12 seconds).
-
Claudio Takahasi authored
Send PropertyChanged(Discovering=FALSE) based on the adapter discovery type. For BR/EDR capable only adapters, after inquiry or periodic inquiry finishes. For LE only, after 5.12 scanning interval. For dual mode adapters, after the interleave interval.
-
Claudio Takahasi authored
Extract the RSSI is necessary to report DeviceFound signal. DeviceFound signals are not emitted if the RSSI value is the same.
-
Claudio Takahasi authored
Advertising data has variable length. Maximum length are 31 bytes. RSSI field is the last byte of the datagram. Declare the data field with fixed length will point the rssi field to an invalid memory address.
-
Vinicius Costa Gomes authored
According to the general discovery procedure should interleave the general discovery procedure over BR/EDR with the general discovery procedure over LE. LE Scanning is reporting found remote devices using DeviceFound signals. Currently, only the Bluetooth address is extracted from the Advertising event. Step 1: BR/EDR discovery for TGAP(100)/2 sec Step 2: LE discovery for TGAP(100)/2 sec
-
Claudio Takahasi authored
Changes hciops plugin to add LE start/stop scanning options and metaevent decoding.
-
Johan Hedberg authored
-
Johan Hedberg authored
-
Anderson Lizardo authored
This is consistent with other att.h functions, and allows length checks.
-
Anderson Lizardo authored
-
Anderson Lizardo authored
att_get_u16() already does a cast of the void* parameter to uint16_t*.
-
Anderson Lizardo authored
-
Johan Hedberg authored
-
Anderson Lizardo authored
This fix makes gatttool exit with non-zero return code on any error.
-
Anderson Lizardo authored
-
Anderson Lizardo authored
-
Anderson Lizardo authored
-