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.\" $Id: ite.4,v 1.1 1994/09/19 17:40:54 chopps Exp $ 38.\" 39.Dd August 30, 1994 40.Dt ITE 4 amiga 41.Os NetBSD 1.0 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.Sh DESCRIPTION 52.Tn TTY 53special files of the form ``ttye?'' 54are interfaces to the 55.Tn Amiga ITE 56for bit-mapped displays. 57An 58.Nm 59is the main system console on most 60.Tn Amiga 61workstations and 62is the mechanism through which a user communicates with the machine. 63If more than one of the supported displays exists on a system, 64any or all can be used as 65.Nm 66.Ns s 67with the limitation that only 68one will have a keyboard (since only one keyboard is supported) and only 69one of each type can be used. 70.Pp 71.Nm Ite 72devices use the 73.Tn HP-UX 74.Sq Li 300h 75.Xr termcap 5 76entry. 77However, as currently implemented, 78the 79.Nm ite 80does not support the full range of 81.Tn HP-UX 82capabilities for this device. 83Missing are multiple colors, blinking, softkeys, 84programmable tabs, scrolling memory and keyboard arrow keys. 85The keyboard will use the left and right 86.Tn Em Amiga 87keys as meta keys, in that it will set the eighth bit of the character code. 88.Nm Ite 89devices also do a good job at emulating the 90.Sq Li vt100 91.Xr termcap 5 92entry. 93.Pp 94Upon booting, the kernel will first look for an 95.Nm ite 96device 97to use as the system console 98.Pq Pa /dev/console . 99If a display exists at any hardware address, it will be the console. 100The kernel looks for, in order: 101.Nm ite2 , 102.Nm ite1 103then 104.Nm ite0 105.Pp 106On most systems, 107a display is used both as an 108.Nm ite 109.Pf ( Pa /dev/ttye? 110aka 111.Pa /dev/console ) 112and as a graphics device 113.Pq /dev/grf? . 114In this environment, 115there is some interaction between the two uses that should be noted. 116For example, opening 117.Pa /dev/grf0 118will deactivate the 119.Nm 120that is, write over whatever may be on the 121.Nm 122display. 123When the graphics application is finished and 124.Pa /dev/grf0 125closed, 126the 127.Nm 128will be reinitialized with the frame buffer cleared 129and the 130old colormap installed. 131.Sh HISTORY 132The 133.Tn Amiga 134.Nm 135first appeared in 136.Nx 0.9a 137.Sh SEE ALSO 138.Xr grf 4 , 139.Xr kbd 4 140