From owner-freebsd-mobile Fri Jan 22 11:46:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00650 for freebsd-mobile-outgoing; Fri, 22 Jan 1999 11:46:45 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00643 for ; Fri, 22 Jan 1999 11:46:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA00993; Fri, 22 Jan 1999 11:41:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901221941.LAA00993@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams cc: Mike Smith , "Gary T. Corcoran" , mobile@FreeBSD.ORG Subject: Re: Reclaiming irqs for unsupported PCI hardware? In-reply-to: Your message of "Fri, 22 Jan 1999 12:40:04 MST." <199901221940.MAA22323@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 22 Jan 1999 11:41:58 -0800 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > > Sure it does. IRQ's are no longer generated on that piece of hardware, > > > but it's possible that the IRQ routine was in the middle of processing > > > the previous (valid) IRQ that was generated 'just prior' to the removal. > > > > Uh, it's also possible for the removal itself to generate an interrupt > > - I had this 100% repeatable on the Sharp I used to use. > > Right, but this does not work reliably on all PCIC controllers. It > works on mine, but I know a number of controllers it does not work on > (for whatever reason). Sorry, you're missing my point - the removal causes a *card* interrupt, not a PCIC interrupt. > > > > In other words, just make sure mobile users know they _must_ > > > > shutdown a card before removing it, and forget about trying to handle > > > > stupid (or accidental) user actions. > > > > > > The use of the IRQ makes it less painful *IF* the user yanks their > > > card. Is it worth making it easier? I don't know. > > > > That's it in a nutshell. > > You got it. If we've got the IRQ, we *can* make it safer. But, it > doesn't work reliably on some hardware, and it 'wastes' an interrupt > that might otherwise be used for something else. (I'm using the term > 'waste' loosely here, since I think it makes the system more robust..) Understood. Hmm. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message