osmocom
/
wireshark
14
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Use FT_UINT40 in two places 

Finally we have FT_UINT40, so used it in Bluetooth ATT and
HDP dissectors.

Change-Id: Iab0e71345f031bca972b1eee20d7e95e193b2aef
Reviewed-on: https://code.wireshark.org/review/10527
Petri-Dish: Michal Labedzki <michal.labedzki@tieto.com>
Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org>
Reviewed-by: Alexis La Goutte <alexis.lagoutte@gmail.com>
This commit is contained in:
Michal Labedzki 2015-09-06 18:15:04 +02:00 committed by Alexis La Goutte
parent fb80cbdd00
commit 3d4ee5e6c1
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
epan/dissectors/packet-btatt.c
View File

@ -5082,10 +5082,9 @@ proto_register_btatt(void)
FT_STRING, BASE_NONE, NULL, 0x0,
NULL, HFILL}
},
/* TODO: FT_UINT40 */
{&hf_btatt_system_id_manufacturer_identifier,
{"Manufacturer Identifier", "btatt.system_id.manufacturer_identifier",
FT_UINT64, BASE_HEX, NULL, 0x0,
FT_UINT40, BASE_HEX, NULL, 0x0,
NULL, HFILL}
},
{&hf_btatt_system_id_organizationally_unique_identifier,

3
epan/dissectors/packet-hdcp.c
View File

@ -262,9 +262,8 @@ proto_register_hdcp(void)
{ &hf_hdcp_resp_to,
{ "Response To", "hdcp.resp_to", FT_FRAMENUM, BASE_NONE, NULL, 0x0,
"This is the response to the request in this frame", HFILL }},
/* actually, the KSVs are only 40bits, but there's no FT_UINT40 type */
{ &hf_hdcp_a_ksv,
{ "Transmitter's key selection vector", "hdcp.a_ksv", FT_UINT64,
{ "Transmitter's key selection vector", "hdcp.a_ksv", FT_UINT40,
BASE_HEX, NULL, 0, NULL, HFILL } },
{ &hf_hdcp_b_ksv,
{ "Receiver's key selection vector", "hdcp.b_ksv", FT_UINT64,