Skip to content

Commit 6f64f77

Browse files
Tronildleach02
authored andcommitted
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>
1 parent b590c0b commit 6f64f77

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

subsys/bluetooth/controller/ll_sw/ull_scan_aux.c

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -361,13 +361,12 @@ void ull_scan_aux_setup(memq_link_t *link, struct node_rx_pdu *rx)
361361

362362
h = (void *)p->ext_hdr_adv_data;
363363

364-
/* Regard PDU as invalid if a RFU field is set, we do not know the
365-
* size of this future field, hence will cause incorrect calculation of
366-
* offset to ACAD field.
364+
/* Note: The extended header contains a RFU flag that could potentially cause incorrect
365+
* calculation of offset to ACAD field if it gets used to add a new header field; However,
366+
* from discussion in BT errata ES-8080 it seems clear that BT SIG is aware that the RFU
367+
* bit can not be used to add a new field since existing implementations will not be able
368+
* to calculate the start of ACAD in that case
367369
*/
368-
if (h->rfu) {
369-
goto ull_scan_aux_rx_flush;
370-
}
371370

372371
ptr = h->data;
373372

0 commit comments

Comments
 (0)