From owner-svn-doc-all@FreeBSD.ORG Tue May 6 20:34:50 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04A5C3CE; Tue, 6 May 2014 20:34:50 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D83BDA6; Tue, 6 May 2014 20:34:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s46KYn4p018743; Tue, 6 May 2014 20:34:49 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s46KYnwS018742; Tue, 6 May 2014 20:34:49 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201405062034.s46KYnwS018742@svn.freebsd.org> From: Dru Lavigne Date: Tue, 6 May 2014 20:34:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44781 - head/en_US.ISO8859-1/books/handbook/serialcomms X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2014 20:34:50 -0000 Author: dru Date: Tue May 6 20:34:49 2014 New Revision: 44781 URL: http://svnweb.freebsd.org/changeset/doc/44781 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Tue May 6 19:47:57 2014 (r44780) +++ head/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml Tue May 6 20:34:49 2014 (r44781) @@ -63,441 +63,435 @@ bps - - Bits per - Secondbits-per-second - (bps) is the rate at which data is - transmitted. - - + + Bits per + Secondbits-per-second + (bps) is the rate at which data is + transmitted. + + - - DTE - - Data Terminal - EquipmentDTE - (DTE) is one of two endpoints in a - serial communication. An example would be a - computer. - - + + DTE + + Data Terminal + EquipmentDTE + (DTE) is one of two endpoints in a + serial communication. An example would be a + computer. + + - - DCE - - Data Communications - EquipmentDCE - (DTE) is the other endpoint in a - serial communication. Typically, it is a modem. - - + + DCE + + Data Communications + EquipmentDCE + (DTE) is the other endpoint in a + serial communication. Typically, it is a modem. + + - - RS-232 + + RS-232 + + The original standard which defined hardware serial + communications. It has since been renamed to + TIA-232RS-232C + cables. + + + - - The original standard which defined hardware serial - communications. It has since been renamed to - TIA-232RS-232C - cables. - - - + When talking about communications data rates, this section + does not use the term baud. Baud refers to the + number of electrical state transitions that may be made in a + period of time, while bps is the + correct term to use. + + To connect a modem or serial terminal to a &os; system, a + serial port on the computer and the proper cable to connect to + the serial device are needed. Users who are already familiar + with serial hardware and cabling can safely skip this + section. + + + Serial Cables and Ports + + There are several different kinds of serial cables. The + two most common types are null-modem cables and standard + RS-232 cables. The documentation for the hardware should + describe the type of cable required. - When talking about communications data rates, this section - does not use the term baud. Baud refers to the - number of electrical state transitions that may be made in a - period of time, while bps is the - correct term to use. - - To connect a modem or serial terminal to a &os; system, a - serial port on the computer and the proper cable to connect to - the serial device are needed. Users who are already familiar - with serial hardware and cabling can safely skip this - section. - - - Serial Cables and Ports - - There are several different kinds of serial cables. The - two most common types are null-modem cables and standard - RS-232 cables. The documentation for the hardware should - describe the type of cable required. + + null-modem cable + - - null-modem cable - + A null-modem cable passes some signals, such as + Signal Ground, straight through, but switches + other signals. For example, the Transmitted + Data pin on one end goes to the Received + Data pin on the other end. + + A null-modem cable can be constructed for use with + terminals. The following table shows the RS-232C signal names and + the pin numbers on a DB-25 connector. While the standard + calls for a straight-through pin 1 to pin 1 + Protective Ground line, it is often + omitted. Some terminals work using only pins 2, 3, and 7, + while others require different configurations than the + examples shown below. - A null-modem cable passes some signals, such as - Signal Ground, straight through, but - switches other signals. For example, the - Transmitted Data pin on one end goes to the - Received Data pin on the other end. - - A null-modem cable can be constructed for use with - terminals. The following table shows the RS-232C signal names - and the pin numbers on a DB-25 connector. While the - standard calls for a straight-through pin 1 to pin 1 - Protective Ground line, it is often - omitted. Some terminals work using only pins 2, 3, and - 7, while others require different configurations than - the examples shown below. - - - DB-25 to DB-25 Null-Modem Cable - - - - - Signal - Pin # - - Pin # - Signal - - - - - - SG - 7 - connects to - 7 - SG - - - - TD - 2 - connects to - 3 - RD - - - - RD - 3 - connects to - 2 - TD - - - - RTS - 4 - connects to - 5 - CTS - - - - CTS - 5 - connects to - 4 - RTS - - - - DTR - 20 - connects to - 6 - DSR - - - - DTR - 20 - connects to - 8 - DCD - - - - DSR - 6 - connects to - 20 - DTR - - - - DCD - 8 - connects to - 20 - DTR - - - -
- - The next two tables show two other common - schemes. - - - DB-9 to DB-9 Null-Modem Cable - - - - - Signal - Pin # - - Pin # - Signal - - - - - - RD - 2 - connects to - 3 - TD - - - - TD - 3 - connects to - 2 - RD - - - - DTR - 4 - connects to - 6 - DSR - - - - DTR - 4 - connects to - 1 - DCD - - - - SG - 5 - connects to - 5 - SG - - - - DSR - 6 - connects to - 4 - DTR - - - - DCD - 1 - connects to - 4 - DTR - - - - RTS - 7 - connects to - 8 - CTS - - - - CTS - 8 - connects to - 7 - RTS - - - -
- - - DB-9 to DB-25 Null-Modem Cable - - - - - Signal - Pin # - - Pin # - Signal - - - - - - RD - 2 - connects to - 2 - TD - - - - TD - 3 - connects to - 3 - RD - - - - DTR - 4 - connects to - 6 - DSR - - - - DTR - 4 - connects to - 8 - DCD - - - - SG - 5 - connects to - 7 - SG - - - - DSR - 6 - connects to - 20 - DTR - - - - DCD - 1 - connects to - 20 - DTR - - - - RTS - 7 - connects to - 5 - CTS - - - - CTS - 8 - connects to - 4 - RTS - - - -
+ + DB-25 to DB-25 Null-Modem Cable - - When one pin at one end connects to a pair of pins - at the other end, it is usually implemented with one - short wire between the pair of pins in their connector - and a long wire to the other single pin. - + + + + Signal + Pin # + + Pin # + Signal + + - The above designs seem to be the most popular. In - another variation, SG connects to SG, TD connects to RD, - RTS and CTS connect to DCD, DTR connects to DSR, and - vice-versa. - - RS-232C cables - - A standard serial cable passes all of the RS-232C - signals straight through. The Transmitted - Data pin on one end of the cable goes to the - Transmitted Data pin on the other end. - This is the type of cable used to connect a modem to - the &os; system, and is also appropriate for some - terminals. - - Serial ports are the devices through which data is - transferred between the &os; host computer and the - terminal. This section describes the kinds of ports that - exist and how they are addressed in &os;. - - Several kinds of serial ports exist. Before - purchasing or constructing a cable, make sure it will - fit the ports on the terminal and on the &os; - system. - - Most terminals have DB-25 ports. Personal computers - may have DB-25 or DB-9 ports. A multiport serial card may - have RJ-12 or RJ-45 ports. - - See the documentation that accompanied the hardware - for specifications on the kind of port or visually verify - the type of port. - - In &os;, each serial port is accessed through an - entry in /dev. - There are two different kinds of entries: + + + SG + 7 + connects to + 7 + SG + - - - Call-in ports are named - /dev/ttyuN - where N is the port number, - starting from zero. Generally, the call-in port is - used for terminals. Call-in ports require that the - serial line assert the Data Carrier Detect - (DCD) signal to work - correctly. - + + TD + 2 + connects to + 3 + RD + - - Call-out ports are named - /dev/cuauN. - Call-out ports are usually not used for terminals, but - are used for modems. The call-out port can be used if - the serial cable or the terminal does not support the - carrier detect signal. - - + + RD + 3 + connects to + 2 + TD + + + + RTS + 4 + connects to + 5 + CTS + + + + CTS + 5 + connects to + 4 + RTS + + + + DTR + 20 + connects to + 6 + DSR + + + + DTR + 20 + connects to + 8 + DCD + + + + DSR + 6 + connects to + 20 + DTR + + + + DCD + 8 + connects to + 20 + DTR + + + +
+ + The next two tables show two other common schemes. + + + DB-9 to DB-9 Null-Modem Cable + + + + + Signal + Pin # + + Pin # + Signal + + + + + + RD + 2 + connects to + 3 + TD + - If a terminal is connected to the first serial - port(COM1), use - /dev/ttyu0 to refer to the - terminal. If the terminal is on the second serial port - (COM2), use - /dev/ttyu1, and so forth. - + + TD + 3 + connects to + 2 + RD + + + + DTR + 4 + connects to + 6 + DSR + + + + DTR + 4 + connects to + 1 + DCD + + + + SG + 5 + connects to + 5 + SG + + + + DSR + 6 + connects to + 4 + DTR + + + + DCD + 1 + connects to + 4 + DTR + + + + RTS + 7 + connects to + 8 + CTS + + + + CTS + 8 + connects to + 7 + RTS + + + +
+ + + DB-9 to DB-25 Null-Modem Cable + + + + + Signal + Pin # + + Pin # + Signal + + + + + + RD + 2 + connects to + 2 + TD + + + + TD + 3 + connects to + 3 + RD + + + + DTR + 4 + connects to + 6 + DSR + + + + DTR + 4 + connects to + 8 + DCD + + + + SG + 5 + connects to + 7 + SG + + + + DSR + 6 + connects to + 20 + DTR + + + + DCD + 1 + connects to + 20 + DTR + + + + RTS + 7 + connects to + 5 + CTS + + + + CTS + 8 + connects to + 4 + RTS + + + +
+ + + When one pin at one end connects to a pair of pins at + the other end, it is usually implemented with one short wire + between the pair of pins in their connector and a long wire + to the other single pin. + + + The above designs seem to be the most popular. In + another variation, SG connects to SG, TD connects to RD, RTS + and CTS connect to DCD, DTR connects to DSR, and + vice-versa. + + RS-232C cables + + A standard serial cable passes all of the RS-232C signals + straight through. The Transmitted Data pin on + one end of the cable goes to the Transmitted + Data pin on the other end. This is the type of + cable used to connect a modem to the &os; system, and is also + appropriate for some terminals. + + Serial ports are the devices through which data is + transferred between the &os; host computer and the terminal. + This section describes the kinds of ports that exist and how + they are addressed in &os;. + + Several kinds of serial ports exist. Before purchasing or + constructing a cable, make sure it will fit the ports on the + terminal and on the &os; system. + + Most terminals have DB-25 ports. Personal computers may + have DB-25 or DB-9 ports. A multiport serial card may have + RJ-12 or RJ-45 ports. + + See the documentation that accompanied the hardware for + specifications on the kind of port or visually verify the type + of port. + + In &os;, each serial port is accessed through an entry in + /dev. There are two different kinds of + entries: + + + + Call-in ports are named + /dev/ttyuN + where N is the port number, + starting from zero. Generally, the call-in port is used + for terminals. Call-in ports require that the serial line + assert the Data Carrier Detect (DCD) + signal to work correctly. + + + + Call-out ports are named + /dev/cuauN. + Call-out ports are usually not used for terminals, but are + used for modems. The call-out port can be used if the + serial cable or the terminal does not support the carrier + detect signal. + + + + If a terminal is connected to the first serial port + (COM1), use + /dev/ttyu0 to refer to the terminal. If + the terminal is on the second serial port + (COM2), use + /dev/ttyu1, and so forth. + Kernel Configuration &os; supports four serial ports by default. In the - &ms-dos; world, these are known as - COM1, - COM2, - COM3, and + &ms-dos; world, these are known as COM1, + COM2, COM3, and COM4. &os; currently supports dumb multiport serial interface cards, such as the BocaBoard 1008 and 2016, as well as more intelligent @@ -505,19 +499,18 @@ Technologies. However, the default kernel only looks for the standard COM ports. - To see if the kernel recognizes the serial ports, - watch for messages while the kernel is booting, or use - /sbin/dmesg to replay the kernel's - boot messages. Look for messages that start with the - characters uart: + To see if the kernel recognizes the serial ports, watch + for messages while the kernel is booting, or use + /sbin/dmesg to replay the kernel's boot + messages. Look for messages that start with the characters + uart: &prompt.root; /sbin/dmesg | grep 'uart' - If the kernel does not recognize all of the serial - ports, configure /boot/device.hints. - When editing this file, one can comment out or completely - remove lines for devices that do not exist on the - system. + If the kernel does not recognize all of the serial ports, + configure /boot/device.hints. When + editing this file, one can comment out or completely remove + lines for devices that do not exist on the system. port IO_COM1 is a substitution for @@ -528,11 +521,10 @@ addresses for their respective serial ports and interrupts 4, 3, 5, and 9 are fairly common interrupt request lines. Regular serial ports cannot share - interrupts on ISA-bus PCs. Multiport boards have - on-board electronics that allow all the 16550A's on the - board to share one or two interrupt request lines. + interrupts on ISA-bus PCs. Multiport boards have on-board + electronics that allow all the 16550A's on the board to + share one or two interrupt request lines. - @@ -614,7 +606,8 @@ of the port will be stuck with 57600 bps. The initial state and lock state devices should only be - writable by root. + writable by root. @@ -641,9 +634,9 @@ connected network. This section describes how to use terminals with &os;. - The original &unix; systems did not have consoles. - Instead, users logged in and ran programs through terminals - that were connected to the computer's serial ports. + The original &unix; systems did not have consoles. Instead, + users logged in and ran programs through terminals that were + connected to the computer's serial ports. The ability to establish a login session on a serial port still exists in nearly every &unix;-like operating system @@ -668,17 +661,18 @@ to computers over serial lines. They are called dumb because they have only enough computational power to display, send, and receive text. - No programs can be run on these devices. Instead, dumb terminals - connect to a computer that runs the needed programs. - - There are hundreds of kinds of dumb terminals made - by many manufacturers, and just about any kind will work - with &os;. Some high-end terminals can even display - graphics, but only certain software packages can take - advantage of these advanced features. + No programs can be run on these devices. Instead, dumb + terminals connect to a computer that runs the needed + programs. + + There are hundreds of kinds of dumb terminals made by + many manufacturers, and just about any kind will work with + &os;. Some high-end terminals can even display graphics, + but only certain software packages can take advantage of + these advanced features. - Dumb terminals are popular in work environments - where workers do not need access to graphical + Dumb terminals are popular in work environments where + workers do not need access to graphical applications. @@ -689,9 +683,8 @@ Since a dumb terminal has just enough ability to display, send, and receive text, any spare computer can be a dumb terminal. All that is needed is the proper - cable and some terminal - emulation software to run on the - computer. + cable and some terminal emulation + software to run on the computer. This configuration can be useful. For example, if one user is busy working at the &os; system's console, another @@ -703,25 +696,27 @@ &os; that can be used to work through a serial connection: &man.cu.1; and &man.tip.1;. - For example, to connect from a client system that runs &os; to the - serial connection of another system: + For example, to connect from a client system that runs + &os; to the serial connection of another system: &prompt.root; cu -l serial-port-device - Replace serial-port-device with the device name of - the connected serial port. These device files are called + Replace serial-port-device + with the device name of the connected serial port. These + device files are called /dev/cuauN on &os; versions 8.x and lower and /dev/cuadN on &os; versions 9.x and higher. In either case, - N is the - serial port number, starting from zero. - This means that COM1 - is /dev/cuau0 or - /dev/cuad0 in &os;. - - Additional programs are available - through the Ports Collection, such as comms/minicom. + N is the serial port number, + starting from zero. This means that + COM1 is + /dev/cuau0 or + /dev/cuad0 in &os;. + + Additional programs are available through the Ports + Collection, such as *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***