FreeCalypso > hg > gsm-codec-lib
comparison doc/EFR-testing @ 158:1e8569000049
doc/EFR-testing: document endian issues
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Thu, 15 Dec 2022 02:18:51 +0000 |
| parents | 170e03b20337 |
| children |
comparison
equal
deleted
inserted
replaced
| 157:04936af99fc8 | 158:1e8569000049 |
|---|---|
| 10 decoder is correct. | 10 decoder is correct. |
| 11 | 11 |
| 12 For debugging, we also have gsmefr-cod-parse and gsmefr-dec-parse utilities that | 12 For debugging, we also have gsmefr-cod-parse and gsmefr-dec-parse utilities that |
| 13 parse ETSI *.cod and *.dec file formats and dump their content in human-readable | 13 parse ETSI *.cod and *.dec file formats and dump their content in human-readable |
| 14 form similar to gsmrec-dump. | 14 form similar to gsmrec-dump. |
| 15 | |
| 16 Please note that all ETSI test sequence file formats are endian-dependent: their | |
| 17 original programs read and write 16-bit words in the local machine's native byte | |
| 18 order, and whenever you are working with published test sequence files, you have | |
| 19 to check to see if they are BE or LE. Our gsmefr-etsi-{enc,dec} and | |
| 20 gsmefr-{cod,dec}-parse programs support both byte orders; the default is LE | |
| 21 (matching the main parts of ts_100725v050200p0.zip), or you can select BE with | |
| 22 -b option. |
