From owner-freebsd-current Mon Jul 21 19:16:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA28096 for current-outgoing; Mon, 21 Jul 1997 19:16:41 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA28083 for ; Mon, 21 Jul 1997 19:16:38 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.6/8.7.3) with SMTP id WAA10202; Mon, 21 Jul 1997 22:15:58 -0400 (EDT) Message-Id: <199707220215.WAA10202@whizzo.TransSys.COM> X-Mailer: exmh version 2.0delta 6/3/97 To: Michael Smith cc: imp@rover.village.org (Warner Losh), sef@Kithrup.COM, current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: I am contemplating the following change... References: <199707211740.DAA24549@genesis.atrad.adelaide.edu.au> In-reply-to: Your message of "Tue, 22 Jul 1997 03:10:00 +0930." <199707211740.DAA24549@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Jul 1997 22:15:58 -0400 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On top of that, working out which interrupt the card is on is not > easy. There isn't some convenient register that you can read for > this. 8( Back in the days when I ran 4.[23]BSD on my VAX 11/750, the autoconfig code planted trap catchers in all the likely interrupts vectors. All you had to do was poke at the device being probed enough to cause an interrupt, any interrupt. I don't seem to recall configuring interrupt vectors in my kernel config, and the good thing about UNIBUS peripherals is that you weren't likely to run out of interrupts. Or am I just dreaming this? louie