[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bluetooth-dev] DLCI 2 vs DLCI 0



When bt_write_top calls rfcomm_send_data the port is hardcoded to 2. But
sometime when I do a connect I seem to get DLCI 0, not DLCI 2, and
rfcomm complains that DLCI 2 is not connected.

What are these DLCI numbers, why do they vary and why is 2 hardcoded? I
see them mentioned in the core spec but it isn't clear to me yet.

Thanks,
--Gordon

-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com