From owner-freebsd-mobile  Fri Mar  6 17:00:41 1998
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA22000
          for freebsd-mobile-outgoing; Fri, 6 Mar 1998 17:00:41 -0800 (PST)
          (envelope-from owner-freebsd-mobile@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21989;
          Fri, 6 Mar 1998 17:00:30 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA11935;
	Sat, 7 Mar 1998 11:57:56 +1100
Date: Sat, 7 Mar 1998 11:57:56 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199803070057.LAA11935@godzilla.zeta.org.au>
To: mike@smith.net.au, nate@mt.sri.com
Subject: Re: sio0: X events for device with no tp
Cc: bde@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG, marko@cs.uni-frankfurt.de
Sender: owner-freebsd-mobile@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>A port is generating interrupts even though it isn't open.  This is 
>typically an artifact of a device which reponsds slowly/differently to 
>the FIFO depth probe.

Leftovers from the probe should be ignored, because the are only noticed
if siointr() or siointr1() is called, and these functions shouldn't be
called because device interrupts are masked.  pccard apparently miswires
the interrupts so that an interrupt (perhaps for another device) is
delivered to siointr().  Perhaps the problem is simply pccard's abuse of
non-fast interrupts.  Non-fast interrupts can be leftover from the probe.
Drivers that support non-fast interrupts and report unexpected interrupts
verbosely should have something to de-verbosify the leftover ones.
E.g., the wd driver.  sio doesn't support non-fast interrupts :-).

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message