From owner-freebsd-hardware  Fri Mar  7 02:40:01 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA02399
          for hardware-outgoing; Fri, 7 Mar 1997 02:40:01 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA02394
          for <freebsd-hardware@freebsd.org>; Fri, 7 Mar 1997 02:39:55 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA11380; Fri, 7 Mar 1997 21:29:30 +1100
Date: Fri, 7 Mar 1997 21:29:30 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703071029.VAA11380@godzilla.zeta.org.au>
To: msmith@atrad.adelaide.edu.au, nate@mt.sri.com
Subject: Re: Problems with 2.1 Probe?
Cc: bde@zeta.org.au, freebsd-hardware@freebsd.org
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> How does one configure a null IRQ?  In the kernel config?  In the boot
>> config?
>
>You don't specify one in the kernel config.  In normal userconfig, set
>the IRQ to zero.  In visual userconfig hit 'x' to get the 'auto' mode.
>(Did that get committed to 2.2?  I can't remember.)

Actually, in normal userconfig, you type ls to get some examples and
then follow one of the examples and set the irq to -1 (irq 0 is for
the clock).  In visual userconfig you give up and send mail to Mike,
since the changes for auto mode haven't been committed to -current.

Bruce