From owner-freebsd-mobile  Tue Oct 21 22:00:58 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA05682
          for mobile-outgoing; Tue, 21 Oct 1997 22:00:58 -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 WAA05672
          for <mobile@freebsd.org>; Tue, 21 Oct 1997 22:00:54 -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 OAA01311;
	Wed, 22 Oct 1997 14:27:35 +0930 (CST)
Message-Id: <199710220457.OAA01311@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
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:37:05 CST."
             <199710220437.WAA08864@rocky.mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 22 Oct 1997 14:27:33 +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)
> 
> Actually, I never had a problem, but many users complained to me about
> this.  And, it made sense because Win95 'does it this way', and they are
> the reference implementation.

Understood.  There's probably a quirk handler somwhere in there for 
this unit, or it's possible that the ESCD data lists it as not 
available.  Still haven't got around to talking to that. 8(

> > 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.
> 
> It's an option, but it still doesn't allow you to specify the interrupt.

Yes; my feelings were that given that it's trying to automatically 
assign one it makes more sense to correct the information it's using 
rather than to heavy-hand it into a choice for which it has no 
justification.

> > 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...)
> 
> *sigh*  Does your laptop have a Cirrus Logic controller?

No.  8(  Toshiba mostly do their own stuff.  The pcic is, I *think*, the
part marked TC183GT6JF.  I seem to recall Tatsumi saying that he had 
tried to get data on this one and failed.  The controller is detected 
as an i82365, FWIW.

mike