From 5f0b8ba01809f6280e1aa250a27fd2c8f2ba0142 Mon Sep 17 00:00:00 2001 From: jeremy Date: Thu, 3 Sep 1998 01:54:28 +0000 Subject: [PATCH] Changed to suggest using sun3/autoconf.h rather than machine/autoconf.h to reflect the new system include file locations. Reworded slightly and added more macros. --- share/man/man9/man9.sun3/isr_add.9 | 33 ++++++++++++++++-------------- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/share/man/man9/man9.sun3/isr_add.9 b/share/man/man9/man9.sun3/isr_add.9 index 865d0f1bd92d..8b6f2b4920b9 100644 --- a/share/man/man9/man9.sun3/isr_add.9 +++ b/share/man/man9/man9.sun3/isr_add.9 @@ -1,4 +1,4 @@ -.\" $NetBSD: isr_add.9,v 1.3 1997/11/11 10:07:47 mrg Exp $ +.\" $NetBSD: isr_add.9,v 1.4 1998/09/03 01:54:28 jeremy Exp $ .\" .\" Copyright (c) 1997 The NetBSD Foundation, Inc. .\" All rights reserved. @@ -44,7 +44,7 @@ .Nm isr_add_custom .Nd establish interrupt handler .Sh SYNOPSIS -.Fd #include +.Fd #include .Bd -literal typedef int (*isr_func_t)(void *); @@ -58,32 +58,35 @@ typedef int (*isr_func_t)(void *); .Sh DESCRIPTION The .Nm -functions establish interrupt handlers into the system interrupt dispatch table, -typically called during the autoconfiguration process for a device. +functions establish interrupt handlers into the system interrupt dispatch table +and are typically called from device drivers during the autoconfiguration +process. .Pp There are two types of interrupts in the Motorola 68000 architecture, which differ in the way that an interrupt request is mapped to a dispatch function within the interrupt vector table. .Pp When the CPU detects an asserted signal on one of its interrupt request lines, -it stops normal instruction execution and begins an interrupt acknowledge -sequence on the system bus. +it suspends normal instruction execution and begins an interrupt acknowledge +cycle on the system bus. During this cycle the interrupting device directs how the CPU is to dispatch -the interrupt request. +its interrupt request. .Pp -If the interrupting device is sophisticated enough, +If the interrupting device is integrated tightly with the system bus, it provides an 8-bit interrupt vector number to the CPU and a -.Dq vectored +.Sy vectored interrupt occurs. This vector number points to a vector entry within the interrupt vector table to which instruction execution is immediately transfered. .Pp -If the interrupting device cannot provide a vector number, it asserts a -specialized bus line and an -.Dq autovectored +If the interrupting device cannot provide a vector number, +it asserts a specialized bus line and an +.Sy autovectored interrupt occurs. -The vector number to use is determined by adding the interrupt priority (0-6) -to an autovector base (typically 0x18). +The vector number to use is determined by adding the interrupt priority +.Pq 0\(en6 +to an autovector base +.Pq typically Li 18 hexadecimal . .Pp .Bl -tag -width isr_add_autovec .It Fn isr_add_autovect @@ -122,7 +125,7 @@ These requirements generally dictate that be written in assembler. .El .Sh "CODE REFERENCES" -.Fd src/sys/arch/sun3/sun3/isr.c +.Pa sys/arch/sun3/sun3/isr.c .Sh "REFERENCES" MC68030 User's Manual, Third edition, MC68030UM/AD Rev 2, Motorola Inc. .Sh "BUGS"