From owner-freebsd-mobile Fri Jan 22 15:16:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00213 for freebsd-mobile-outgoing; Fri, 22 Jan 1999 15:16:42 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00198 for ; Fri, 22 Jan 1999 15:16:40 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA13120; Fri, 22 Jan 1999 16:16:16 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA23362; Fri, 22 Jan 1999 16:16:15 -0700 Date: Fri, 22 Jan 1999 16:16:15 -0700 Message-Id: <199901222316.QAA23362@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Nate Williams , Mike Smith , "Gary T. Corcoran" , mobile@FreeBSD.ORG Subject: Re: Reclaiming irqs for unsupported PCI hardware? In-Reply-To: <5072.917040083@critter.freebsd.dk> References: <199901221950.MAA22394@mt.sri.com> <5072.917040083@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid 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. > > > >Ah, gotcha. FWIW, supposedly the PCIC interrupt supercedes the card > >interrupt in the current code. :) > > Yes, but that doesn't help you if the current context is a section of code > with interrupts masked/disabled... Exactly. This is why the current PCCARD code can still lockup if your in the middle of doing a SLIP/PPP download and you yank the card out. :( > Anyway, I belive that the "->gone" hack in sio.c is probably as > far as it pays to go down this path anyway. Totally agreed. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message