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

Typos

Browse Source
This commit is contained in:
Nick Patavalis
2018-02-20 13:47:02 +02:00
parent ee23af0cb9
commit 3eae4b37c9
2 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -334,22 +334,24 @@ baudrate values (like 1234, or 42000, etc) to a serial port, provided
that the underlying driver can handle this. Since release 2.0, picocom that the underlying driver can handle this. Since release 2.0, picocom
can be compiled with custom baudrate support for some systems. Since can be compiled with custom baudrate support for some systems. Since
release 3.1 picocom is compiled with custom baudrate support enabled release 3.1 picocom is compiled with custom baudrate support enabled
by default on some systems (like Linux, kernels > 2.6, on ix86 and *by default* on some systems (like Linux, kernels > 2.6, on x86 and
ix86_64, modern intel macs, and some other BSDs). In any case, you can x86_64, modern Intel Macs, and some BSDs). In any case, you can
explicitly ask for custom baudrate support to be enabled by compiling explicitly ask for custom baudrate support to be *enabled* by
picocom like this: compiling picocom like this:
CPPFLAGS=-DUSE_CUSTOM_BAUD make clean CPPFLAGS=-DUSE_CUSTOM_BAUD make clean
CPPFLAGS=-DUSE_CUSTOM_BAUD make CPPFLAGS=-DUSE_CUSTOM_BAUD make
If custom baudrate support is not available for your system, the If custom baudrate support is not available for your system, the
compilation will fail. Similarly, you can ask for custom baudrate compilation will fail. Similarly, you can ask for custom baudrate
support to be disabled by compiling like: support to be *disabled* by compiling like:
CPPFLAGS=-DNO_CUSTOM_BAUD make clean CPPFLAGS=-DNO_CUSTOM_BAUD make clean
CPPFLAGS=-DNO_CUSTOM_BAUD make CPPFLAGS=-DNO_CUSTOM_BAUD make
When picocom is compiled with custom baudrate support on Linux, it (or you can comment in or out the respective lines in the Makefile)
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, TCSETSF, etc)
to access the serial ports. It is not impossible that some serial to access the serial ports. It is not impossible that some serial
devices may not accept these new ioctl's (though they should). In devices may not accept these new ioctl's (though they should). In

2
termios2.txt
View File

@ -156,7 +156,7 @@ CBAUD = 0010017 ---> 0001 0000 0000 1111 mask
CBUADEX = 0010000 ---> 0001 0000 0000 0000 extender bit CBUADEX = 0010000 ---> 0001 0000 0000 0000 extender bit
BOTHER = 0010000 ---> 0001 0000 0000 0000 a reserved code BOTHER = 0010000 ---> 0001 0000 0000 0000 a reserved code
Usually CBAUD includes CBAUDEX. In any case the mask is always CBAUD & Usually CBAUD includes CBAUDEX. In any case the mask is always CBAUD |
CBAUDEX (which is usually == CBAUD) CBAUDEX (which is usually == CBAUD)
Basic codes (Bxxx & CBAUDEX == 0) Basic codes (Bxxx & CBAUDEX == 0)