From owner-freebsd-current  Mon Jul 21 10:21:31 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id KAA26036
          for current-outgoing; Mon, 21 Jul 1997 10:21:31 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA26027
          for <current@freebsd.org>; Mon, 21 Jul 1997 10:21:24 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wqM8x-0001jT-00; Mon, 21 Jul 1997 11:21:07 -0600
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: I am contemplating the following change... 
Cc: Sean Eric Fagan <sef@Kithrup.COM>, current@freebsd.org
In-reply-to: Your message of "Sat, 19 Jul 1997 18:24:11 PDT."
		<22424.869361851@time.cdrom.com> 
References: <22424.869361851@time.cdrom.com>  
Date: Mon, 21 Jul 1997 11:21:07 -0600
From: Warner Losh <imp@rover.village.org>
Message-Id: <E0wqM8x-0001jT-00@rover.village.org>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <22424.869361851@time.cdrom.com> "Jordan K. Hubbard" writes:
: The ed1 entry is also the cause of much tech support for me since
: it "catches" cards at 0x300 but invariably with the wrong IRQ, so the
: user is tricked into thinking that things work until the install
: is well underway and the only message they're now seeing is:
: "ed1: device timeout" from the bogus IRQ value.

That's a different problem that should be fixed :-).

Warner