From owner-freebsd-mobile  Tue Oct 21 21:32:53 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA04216
          for mobile-outgoing; Tue, 21 Oct 1997 21:32:53 -0700 (PDT)
          (envelope-from owner-freebsd-mobile)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA04210
          for <mobile@freebsd.org>; Tue, 21 Oct 1997 21:32:48 -0700 (PDT)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id NAA01198;
	Wed, 22 Oct 1997 13:58:55 +0930 (CST)
Message-Id: <199710220428.NAA01198@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Nate Williams <nate@mt.sri.com>
cc: Mike Smith <mike@smith.net.au>, mobile@freebsd.org,
        handy@sag.space.lockheed.com
Subject: Re: Patches from -current for -stable I'd like to commit after testing 
In-reply-to: Your message of "Tue, 21 Oct 1997 22:18:50 CST."
             <199710220418.WAA08580@rocky.mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 Oct 1997 13:58:55 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > (One killer is that the code now allocates IRQ 11 by default for the 
> >  pcic, but IRQ 11 is used by "something" else that's not probed.
> 
> I changed the code to use the 'highest' un-allocated IRQ, because that's
> what Win95 does and many machines used built-in IRQ's for IRQ 3.

Understood entirely; all I meant was that you moved the problem from 
your machine to mine.  8)

> >  There 
> >  needs to be a mechanism for explicitly specifying an IRQ for the pcic.)
> 
> Yes, there does.  But, because of the current 'ISA' leanings of the
> configuration, there isn't an easy way.

I hacked an option into kern_intr that allows you to specify a mask of 
interrupts that can never be allowed on the system; this seemed to 
work pretty well.

> In the meantime, you could try backing out the change I made to see if
> things start working again.

I did that; it didn't help.  I need to spend some more time chasing 
kernel builds; I just don't have that right now.  (Assignments, exams, 
new product lagging on a solid deadline...)

mike