[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bluetooth-dev] SCO handle - Ambiguity in Size
Le Vendredi 10 Août 2001 11:37, Akshay Agarwal a écrit :
> Consider the following cases.
> Case 1:
> From TCS :7.4.14
> The purpose of the SCO handle information element is to enable the remote
> side to associate the established SCO link with the ongoing call. The SCO
> handle is identical to the SCO handle exchanged in the LMP_SCO_link_req
> sent by the piconet master (see LMP, Section 3.21 on page 226).
> From Fig 7.20 it was derived that the SCO handle is considered to be a
> single byte. Which is equal to LMP SCO handle value u_int8.
> Case 2:
> However in the HCI Connection Complete Event ., the Connection_handle
> whatever it returns is 12bits. (Sec 5.2.3 HCI Functional Specification)
> Since this is the handle which will be returned as a parameter when we
> issue Add_SCO_Connection, we derive to the conclusion as size of SCO handle
> Thus from Case 1 and Case 2 we reach to two conclusions for size of SCO
> handle of which case 2 forming superset over Case 1.
> Now if we follow case 2 i.e., 12bits, how would we send the SCO_HANDLE in
> TCS as its specifications mandate this size to be just 8bits ?
I guess the stack would only use the 8 LSB of the handle sent by TCS...
> Thanks and Regards,
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com