uzix/picocom
1
0
Fork 0
mirror of https://github.com/UzixLS/picocom.git synced 2025-07-19 07:21:18 +03:00
Code Issues Projects Releases Wiki Activity

Minor rewording

Browse Source
This commit is contained in:
Nick Patavalis
2018-02-20 15:26:40 +02:00
parent 3eae4b37c9
commit 007811c337
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -352,13 +352,13 @@ support to be *disabled* by compiling like:
(or you can comment in or out the respective lines in the Makefile) (or you can comment in or out the respective lines in the Makefile)
When picocom is compiled with custom baudrate support *on Linux*, it When picocom is compiled with custom baudrate support *on Linux*, it
uses a new set of ioctl's (TCGETS2, TCSETSF2 vs TCGETS, TCSETSF, etc) uses a new set of ioctl's (`TCGETS2`, `TCSETSF2` vs `TCGETS`,
to access the serial ports. It is not impossible that some serial `TCSETSF`, etc) to access the serial ports. It is not impossible that
devices may not accept these new ioctl's (though they should). In some systems or some serial devices may not accept these new ioctl's
order to be able to use picocom even with such devices, and without (though they should). In order to be able to use picocom even in this
recompiling it, you can disable the custom baudrate support at case, and without recompiling it, you can disable the custom baudrate
runtime, and force picocom to use the "old" ioctls. To do this support at runtime, and force picocom to use the "old" ioctls. To do
(starting with release 3.2) just define the environment variable this (starting with release 3.2) just define the environment variable
`NO_CUSTOM_BAUD` before running picocom. Something like this: `NO_CUSTOM_BAUD` before running picocom. Something like this:
NO_CUSTOM_BAUD=1 picocom ... NO_CUSTOM_BAUD=1 picocom ...