Lines Matching full:message

43 	#   <op>[,<mode>] rx-nack              NACK the message instead of sending an ACK
45 	#   <op>[,<mode>] rx-add-byte          add a spurious byte to the received CEC message
46 	#   <op>[,<mode>] rx-remove-byte       remove the last byte from the received CEC message
47 	#   <op>[,<mode>] rx-arb-lost <poll>   generate a POLL message to trigger an arbitration lost
58 	#   <op>[,<mode>] tx-add-bytes <num>   append <num> (1-255) spurious bytes to the message
59 	#   <op>[,<mode>] tx-remove-byte       drop the last byte from the message
69 	# <op>       CEC message opcode (0-255) or 'any'
71 	# <bit>      CEC message bit (0-159)
73 	# <poll>     CEC poll message used to test arbitration lost (0x00-0xff, default 0x0f)
99 received or transmitted message, ``always`` to always trigger the error
103 So '``any rx-nack``' will NACK the next received CEC message,
105 '``0x82,toggle rx-nack``' will only NACK if an Active Source message was
106 received and do that only for every other received message.
155     Every byte of the message will be NACKed in case the transmitter
168     Add a spurious 0x55 byte to the received CEC message, provided
169     the message was 15 bytes long or less. This is useful to test
173     Remove the last byte from the received CEC message, provided it
178     Generate a POLL message to trigger an Arbitration Lost condition.
181     to transmit mode and it will transmit a POLL message. By default this is
186     start sending a message at the same time. In that case the initiator
200     specification also allows that the full message is transmitted and only
206     transmitters that ignore NACKs until the very end of the message.
209     Don't set the EOM bit. Normally the last byte of the message has the EOM
210     (End-Of-Message) bit set. With this command the transmit will just stop
219     this case. Since the resulting message is likely to be too short for this
220     same reason the whole message is typically ignored. The receiver should be
224     Append ``<num>`` (1-255) spurious bytes to the message. The extra bytes
225     have the value of the byte position in the message. So if you transmit a
226     two byte message (e.g. a Get CEC Version message) and add 2 bytes, then
227     the full message received by the remote CEC adapter is
231     what does it do when it receives more than the maximum message size of 16
235     Drop the last byte from the message, provided the message is at least
294     reacts when a message just suddenly stops. It should time out and go back