diff options
| author | Gerhard Sittig <gerhard.sittig@gmx.net> | 2018-11-24 11:57:38 +0100 |
|---|---|---|
| committer | Uwe Hermann <uwe@hermann-uwe.de> | 2018-11-25 10:57:09 +0100 |
| commit | 30d27bd438ce90162ffa4911bc61a9661db3d39f (patch) | |
| tree | e104f7f90d42d0aa2989b30a98895d9468b96dee /decoders/uart | |
| parent | 961707103bb0323e6187d81a762f22417fe23dea (diff) | |
| download | libsigrokdecode-30d27bd438ce90162ffa4911bc61a9661db3d39f.tar.gz libsigrokdecode-30d27bd438ce90162ffa4911bc61a9661db3d39f.zip | |
uart: remove obsolete TODO (Python annotation for frame errors)
The "Frame error?" TODO comment on Python annotations has become
obsolete. Individual bit errors within the frame immediately get
communicated as they are detected (START, parity, STOP). The overall
frame's validity has become available with the FRAME annotation.
Diffstat (limited to 'decoders/uart')
| -rw-r--r-- | decoders/uart/pd.py | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/decoders/uart/pd.py b/decoders/uart/pd.py index f89c6e5..4bb68a4 100644 --- a/decoders/uart/pd.py +++ b/decoders/uart/pd.py @@ -39,7 +39,6 @@ This is the list of <ptype>s and their respective <pdata> values: - 'INVALID STOPBIT': The data is the (integer) value of the stop bit (0/1). - 'PARITY ERROR': The data is a tuple with two entries. The first one is the expected parity value, the second is the actual parity value. - - TODO: Frame error? - 'BREAK': The data is always 0. - 'FRAME': The data is always a tuple containing two items: The (integer) value of the UART data, and a boolean which reflects the validity of the |