From owner-freebsd-stable Mon Dec 15 10:45:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24579 for stable-outgoing; Mon, 15 Dec 1997 10:45:39 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24574 for ; Mon, 15 Dec 1997 10:45:34 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon.ghostwheel.com (avalon.ghostwheel.com [207.201.56.88]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id KAA01261; Mon, 15 Dec 1997 10:44:17 -0800 (PST) Message-Id: <3.0.5.32.19971215104217.0093aa00@amber.ghostwheel.com> X-Sender: merlin@amber.ghostwheel.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 15 Dec 1997 10:42:17 -0800 To: Bruce Evans , stable@FreeBSD.ORG From: Christopher Knight Subject: Re: sysinstall/qcam problem with 2.2-stable In-Reply-To: <199712151213.XAA28082@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:13 PM 12/15/97 +1100, Bruce Evans wrote: >> Dec 15 00:28:28 amber /kernel: stray irq 7 > >This is probably correct behaviour. Using irq 7 in a driver breaks >reporting of stray interrupts. This may be a dumb newbie question... but why is a stray interrupt 7 generated when sysinstall is run? >> OK, I modified the qcam0 device to snag irq 7 in the same manner >>that was used for the now disabled lpt0: >> >>device qcam0 at isa? port "IO_LPT1" tty irq 7 > >Don't do that. qcam doesn't use interrupts, and this line is missing >a vector for the interrupt. The configuration error is not detected >by config, and this line happens to be equivalent to: > >device qcam0 at isa? port "IO_LPT1" tty irq 7 vector 0 Thank you for the explanation. I knew there is a reason I should not be tweaking my box, in areas I have little experience, when I'm having a sleepless night. :) -ck