Bluetooth: Controller: Remove incorrect check of RFU bit
RFU bits has to be ignored according to the spec; In addition, some MediaTek devices seems to have it set (by mistake I assume), so having the check means we cannot sync to these devices Signed-off-by: Troels Nilsson <trnn@demant.com>
This commit is contained in:
parent
b590c0b1f6
commit
6f64f77557
1 changed files with 5 additions and 6 deletions
|
@ -361,13 +361,12 @@ void ull_scan_aux_setup(memq_link_t *link, struct node_rx_pdu *rx)
|
||||||
|
|
||||||
h = (void *)p->ext_hdr_adv_data;
|
h = (void *)p->ext_hdr_adv_data;
|
||||||
|
|
||||||
/* Regard PDU as invalid if a RFU field is set, we do not know the
|
/* Note: The extended header contains a RFU flag that could potentially cause incorrect
|
||||||
* size of this future field, hence will cause incorrect calculation of
|
* calculation of offset to ACAD field if it gets used to add a new header field; However,
|
||||||
* offset to ACAD field.
|
* from discussion in BT errata ES-8080 it seems clear that BT SIG is aware that the RFU
|
||||||
|
* bit can not be used to add a new field since existing implementations will not be able
|
||||||
|
* to calculate the start of ACAD in that case
|
||||||
*/
|
*/
|
||||||
if (h->rfu) {
|
|
||||||
goto ull_scan_aux_rx_flush;
|
|
||||||
}
|
|
||||||
|
|
||||||
ptr = h->data;
|
ptr = h->data;
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue