Attachment 37901 Details for Bug 65443

patch to avoid nasty warnings about line breakage/adjusting

open.n.dif (text/plain), 6.54 KB, created by Dr. Werner Fink on 2005-05-23 13:45:10 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Dr. Werner Fink

Created: 2005-05-23 13:45:10 UTC

Size: 6.54 KB

patch

obsolete

>--- -	2005-05-23 15:43:04.964041000 +0200
>+++ open.n	2005-05-23 15:42:19.866972098 +0200
>@@ -386,8 +386,10 @@
> .PP
> The \fBfconfigure\fR command can be used to query and set additional
> configuration options specific to serial ports (where supported):
>+.VE
> .TP
> \fB\-mode\fR \fIbaud\fB,\fIparity\fB,\fIdata\fB,\fIstop\fR
>+.VS 8.4
> This option is a set of 4 comma-separated values: the baud rate, parity,
> number of data bits, and number of stop bits for this serial port.  The
> \fIbaud\fR rate is a simple integer that specifies the connection speed.
>@@ -396,8 +398,10 @@
> ``odd'', ``even'', ``mark'', or ``space''.  \fIData\fR is the number of
> data bits and should be an integer from 5 to 8, while \fIstop\fR is the
> number of stop bits and should be the integer 1 or 2.
>+.VE
> .TP
> \fB\-handshake\fR \fItype\fR
>+.VS 8.4
> (Windows and Unix). This option is used to setup automatic handshake
> control. Note that not all handshake types maybe supported by your operating
> system. The \fItype\fR parameter is case-independent.
>@@ -411,13 +415,17 @@
> There is no default handshake configuration, the initial value depends
> on your operating system settings.
> The \fB-handshake\fR option cannot be queried.
>+.VE
> .TP
> \fB\-queue\fR
>+.VS 8.4
> (Windows and Unix). The \fB-queue\fR option can only be queried.
> It returns a list of two integers representing the current number
> of bytes in the input and output queue respectively.
>+.VE
> .TP
> \fB\-timeout\fR \fImsec\fR
>+.VS 8.4
> (Windows and Unix). This option is used to set the timeout for blocking
> read operations. It specifies the maximum interval between the
> reception of two bytes in milliseconds.
>@@ -425,8 +433,10 @@
> The \fB-timeout\fR option does not affect write operations or
> nonblocking reads.
> This option cannot be queried.
>+.VE
> .TP
> \fB\-ttycontrol\fR \fI{signal boolean signal boolean ...}\fR
>+.VS 8.4
> (Windows and Unix). This option is used to setup the handshake
> output lines (see below) permanently or to send a BREAK over the serial line.
> The \fIsignal\fR names are case-independent.
>@@ -437,39 +447,49 @@
> with active hardware handshake \fBrtscts\fR (or \fBdtrdsr\fR).
> The result is unpredictable.
> The \fB-ttycontrol\fR option cannot be queried.
>+.VE
> .TP
> \fB\-ttystatus\fR
>+.VS 8.4
> (Windows and Unix). The \fB-ttystatus\fR option can only be
> queried.  It returns the current modem status and handshake input signals
> (see below).
> The result is a list of signal,value pairs with a fixed order,
> e.g. \fB{CTS 1 DSR 0 RING 1 DCD 0}\fR.
> The \fIsignal\fR names are returned upper case.
>+.VE
> .TP
> \fB\-xchar\fR \fI{xonChar xoffChar}\fR
>+.VS 8.4
> (Windows and Unix). This option is used to query or change the software
> handshake characters. Normally the operating system default should be
> DC1 (0x11) and DC3 (0x13) representing the ASCII standard
> XON and XOFF characters.
>+.VE
> .TP
> \fB\-pollinterval\fR \fImsec\fR
>+.VS 8.4
> (Windows only). This option is used to set the maximum time between
> polling for fileevents.
> This affects the time interval between checking for events throughout the Tcl
> interpreter (the smallest value always wins).  Use this option only if
> you want to poll the serial port more or less often than 10 msec
> (the default).
>+.VE
> .TP
> \fB\-sysbuffer\fR \fIinSize\fR
> .TP
> \fB\-sysbuffer\fR \fI{inSize outSize}\fR
>+.VS 8.4
> (Windows only). This option is used to change the size of Windows
> system buffers for a serial channel. Especially at higher communication
> rates the default input buffer size of 4096 bytes can overrun
> for latent systems. The first form specifies the input buffer size,
> in the second form both input and output buffers are defined.
>+.VE
> .TP
> \fB\-lasterror\fR
>+.VS 8.4
> (Windows only). This option is query only.
> In case of a serial communication error, \fBread\fR or \fBputs\fR
> returns a general Tcl file I/O error.
>@@ -487,30 +507,44 @@
> names (DCD, RI) come from modems. Of course your external device may use
> these signal lines for other purposes.
> 
>+.VE
> .IP \fBTXD(output)\fR
> \fBTransmitted Data:\fR Outgoing serial data.
> .IP \fBRXD(input)\fR
> \fBReceived Data:\fRIncoming serial data.
> .IP \fBRTS(output)\fR
>+.VS 8.4
> \fBRequest To Send:\fR This hardware handshake line informs the modem that
> your workstation is ready to receive data. Your workstation may
> automatically reset this signal to indicate that the input buffer is full.
>+.VE
> .IP \fBCTS(input)\fR
>+.VS 8.4
> \fBClear To Send:\fR The complement to RTS. Indicates that the modem is
> ready to receive data.
>+.VE
> .IP \fBDTR(output)\fR
>+.VS 8.4
> \fBData Terminal Ready:\fR This signal tells the modem that the workstation
> is ready to establish a link. DTR is often enabled automatically whenever a
> serial port is opened.
>+.VE
> .IP \fBDSR(input)\fR
>+.VS 8.4
> \fBData Set Ready:\fR The complement to DTR. Tells the workstation that the
> modem is ready to establish a link.
>+.VE
> .IP \fBDCD(input)\fR
>+.VS 8.4
> \fBData Carrier Detect:\fR This line becomes active when a modem detects
> a "Carrier" signal.
>+.VE
> .IP \fBRI(input)\fR
>+.VS 8.4
> \fBRing Indicator:\fR Goes active when the modem detects an incoming call.
>+.VE
> .IP \fBBREAK\fR
>+.VS 8.4
> A BREAK condition is not a hardware signal line, but a logical zero on the
> TXD or RXD lines for a long period of time, usually 250 to 500
> milliseconds.  Normally a receive or transmit data signal stays at the mark
>@@ -528,33 +562,45 @@
> general file I/O error.  Then \fBfconfigure -lasterror\fR may help to
> locate the problem.  The following error codes may be returned.
> 
>+.VE
> .TP 10
> \fBRXOVER\fR
>+.VS 8.4
> Windows input buffer overrun. The data comes faster than your scripts reads
> it or your system is overloaded. Use \fBfconfigure -sysbuffer\fR to avoid a
> temporary bottleneck and/or make your script faster.
>+.VE
> .TP 10
> \fBTXFULL\fR
>+.VS 8.4
> Windows output buffer overrun. Complement to RXOVER. This error should
> practically not happen, because Tcl cares about the output buffer status.
>+.VE
> .TP 10
> \fBOVERRUN\fR
>+.VS 8.4
> UART buffer overrun (hardware) with data lost.
> The data comes faster than the system driver receives it.
> Check your advanced serial port settings to enable the FIFO (16550) buffer
> and/or setup a lower(1) interrupt threshold value.
>+.VE
> .TP 10
> \fBRXPARITY\fR
>+.VS 8.4
> A parity error has been detected by your UART.
> Wrong parity settings with \fBfconfigure -mode\fR or a noisy data line (RXD)
> may cause this error.
>+.VE
> .TP 10
> \fBFRAME\fR
>+.VS 8.4
> A stop-bit error has been detected by your UART.
> Wrong mode settings with \fBfconfigure -mode\fR or a noisy data line (RXD)
> may cause this error.
>+.VE
> .TP 10
> \fBBREAK\fR
>+.VS 8.4
> A BREAK condition has been detected by your UART (see above).
> .VE
>

Actions: View

Attachments on bug 65443: 37901 | 85379 | 85380 | 85381