/external/tcpdump/tests/ |
lmp.out | 3 IP 10.0.12.1.49998 > 10.0.12.2.49998: LMPv1 Config NACK Message, length: 56 7 IP 10.0.12.1.49998 > 10.0.12.2.49998: LMPv1 Link Summary NACK Message, length: 96 9 IP 10.0.12.1.49998 > 10.0.12.2.49998: LMPv1 Begin Verify NACK Message, length: 32
|
lmp-v.out | 27 LMPv1, msg-type: Config NACK, Flags: [none], length: 56 73 LMPv1, msg-type: Link Summary NACK, Flags: [none], length: 96 114 LMPv1, msg-type: Begin Verify NACK, Flags: [none], length: 32
|
/external/libnfc-nci/src/nfa/int/ |
nfa_rw_int.h | 314 /* Reactivating type 2 tag after NACK rsp */ 315 tRW_EVENT halt_event; /* Event ID from stack after NACK response */ 316 tRW_DATA rw_data; /* Event Data from stack after NACK response */
|
/external/libnl/include/netlink/ |
netlink-kernel.h | 156 * structure. This can be looked at as a NACK and typically it is
|
/external/tcpdump/ |
print-mpcp.c | 104 { 4, "NACK" }, 129 { 0, "NACK" },
|
print-lmp.c | 184 { LMP_MSGTYPE_CONFIG_NACK, "Config NACK"}, 188 { LMP_MSGTYPE_VERIFY_BEGIN_NACK, "Begin Verify NACK"}, 197 { LMP_MSGTYPE_LINK_SUMMARY_NACK, "Link Summary NACK"}, 204 { LMP_MSGTYPE_SERVICE_CONFIG_NACK, "Service Config NACK"},
|
print-arp.c | 109 { ARPOP_NAK, "NACK Reply" },
|
print-ppp.c | 136 {CPCODES_CONF_NAK, "Conf-Nack"}, 395 { PAP_ANAK, "Auth-NACK" }, [all...] |
print-bootp.c | 349 { DHCPNAK, "NACK" },
|
print-rx.c | [all...] |
/packages/apps/Nfc/nci/jni/ |
NfcTag.h | 239 ** Description: Whether the response is a T2T NACK response. 245 ** Returns: True if the response is NACK
|
NfcTag.cpp | [all...] |
NativeNfcTag.cpp | 901 //responds with a NACK. Need to perform a "reconnect" operation 917 } // else a nack is treated as a transceive failure to the upper layers [all...] |
/external/wpa_supplicant_8/src/wps/ |
wps_i.h | 105 * config_error - Configuration Error value to be used in NACK
|
wps_enrollee.c | [all...] |
/external/lldb/source/Plugins/Process/gdb-remote/ |
GDBRemoteCommunication.h | 162 // For single char packets for ack, nack and /x03
|
GDBRemoteCommunication.cpp | 407 // byte that is a '+' (ACK), '-' (NACK), \x03 (CTRL+C interrupt), 490 // Send the ack or nack if needed
|
/external/lldb/tools/debugserver/source/ |
RNBRemote.h | 40 nack, // '-' enumerator in enum:RNBRemote::__anon14400
|
/external/libnfc-nci/src/nfa/rw/ |
nfa_rw_act.c | 415 NFA_TRACE_DEBUG0("nfa_rw_handle_sleep_wakeup_rsp; Handle the NACK rsp received now"); 437 /* The current operation failed with NACK rsp from type 2 tag */ 441 /* Got NACK rsp during presence check and legacy presence check performed */ 722 /* Received NACK. Let DM wakeup the tag first (by putting tag to sleep and then waking it up) */ [all...] |
/frameworks/av/media/libstagefright/wifi-display/rtp/ |
RTPSender.cpp | 698 return ERROR_UNSUPPORTED; // We only support NACK for now.
|
/external/libnfc-nci/src/nfc/include/ |
tags_defs.h | 184 #define T2T_RSP_NACK1 0x1 /* Nack can be either 1 */
|
rw_api.h | 510 ** packet 1. If a NACK is received as the response, the callback [all...] |
/external/libnfc-nci/src/nfc/int/ |
rw_int.h | 314 BOOLEAN check_tag_halt; /* Resent command after NACK rsp to find tag is in HALT State */ [all...] |
/external/libnl/lib/ |
msg.c | 79 * This message is actually used to denote both an ACK and a NACK.
|
/external/lldb/scripts/ |
disasm-gdb-remote.pl | [all...] |