1.\" Copyright (c) 1990, 1991 The Regents of the University of California. 2.\" All rights reserved. 3.\" 4.\" This code is derived from software contributed to Berkeley by 5.\" the Systems Programming Group of the University of Utah Computer 6.\" Science Department. 7.\" 8.\" Redistribution and use in source and binary forms, with or without 9.\" modification, are permitted provided that the following conditions 10.\" are met: 11.\" 1. Redistributions of source code must retain the above copyright 12.\" notice, this list of conditions and the following disclaimer. 13.\" 2. Redistributions in binary form must reproduce the above copyright 14.\" notice, this list of conditions and the following disclaimer in the 15.\" documentation and/or other materials provided with the distribution. 16.\" 3. All advertising materials mentioning features or use of this software 17.\" must display the following acknowledgement: 18.\" This product includes software developed by the University of 19.\" California, Berkeley and its contributors. 20.\" 4. Neither the name of the University nor the names of its contributors 21.\" may be used to endorse or promote products derived from this software 22.\" without specific prior written permission. 23.\" 24.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 25.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 26.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 27.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 28.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 29.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 30.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 31.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 32.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 33.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 34.\" SUCH DAMAGE. 35.\" 36.\" from: @(#)ite.4 5.2 (Berkeley) 3/27/91 37.\" $NetBSD: ite.4,v 1.8 2001/10/28 18:47:03 wiz Exp $ 38.\" 39.Dd August 30, 1994 40.Dt ITE 4 amiga 41.Os 42.Sh NAME 43.Nm ite 44.Nd 45.Tn Amiga 46Internal Terminal Emulator 47.Sh SYNOPSIS 48.Cd "ite0 at grf0" 49.Cd "ite1 at grf1" 50.Cd "ite2 at grf2" 51.Cd "ite3 at grf3" 52.Cd "ite4 at grf4" 53.Cd "ite5 at grf5" 54.Cd "ite6 at grf6" 55.Cd "ite7 at grf7" 56.Sh DESCRIPTION 57.Tn TTY 58special files of the form ``ttye?'' 59are interfaces to the 60.Tn Amiga ITE 61for bit-mapped displays. 62An 63.Nm 64is the main system console on most 65.Tn Amiga 66workstations and 67is the mechanism through which a user communicates with the machine. 68If more than one of the supported displays exists on a system, 69any or all can be used as 70.Nm 71.Ns s 72with the limitation that only 73one will have a keyboard (since only one keyboard is supported) and only 74one of each type can be used. 75.Pp 76.Nm 77devices use the 78.Tn HP-UX 79.Sq Li 300h 80.Xr termcap 5 81entry. 82However, as currently implemented, 83the 84.Nm 85does not support the full range of 86.Tn HP-UX 87capabilities for this device. 88Missing are multiple colors, blinking, softkeys, 89programmable tabs, scrolling memory and keyboard arrow keys. 90The keyboard will use the left and right 91.Tn Em Amiga 92keys as meta keys, in that it will set the eighth bit of the character code. 93.Nm 94devices also do a good job at emulating the 95.Sq Li vt100 96.Xr termcap 5 97entry. 98.Pp 99Upon booting, the kernel will first look for an 100.Nm 101device 102to use as the system console 103.Pq Pa /dev/console . 104If a display exists at any hardware address, it will be the console. 105The kernel looks for them in decreasing order (that is, choosing the 106highest-numbered one). 107.Pp 108On most systems, 109a display is used both as an 110.Nm 111.Pf ( Pa /dev/ttye? 112aka 113.Pa /dev/console ) 114and as a graphics device 115.Pq /dev/grf? . 116In this environment, 117there is some interaction between the two uses that should be noted. 118For example, opening 119.Pa /dev/grf0 120will deactivate the 121.Nm 122that is, write over whatever may be on the 123.Nm 124display. 125When the graphics application is finished and 126.Pa /dev/grf0 127closed, 128the 129.Nm 130will be reinitialized with the frame buffer cleared 131and the 132old colormap installed. 133.Sh SEE ALSO 134.Xr grf 4 , 135.Xr kbd 4 136.Sh HISTORY 137The 138.Tn Amiga 139.Nm 140first appeared in 141.Nx 1.0 142