Date: Thu, 2 Dec 1999 09:18:18 -0700 From: Nate Williams <nate@mt.sri.com> To: Warner Losh <imp@village.org> Cc: Mike Smith <msmith@FreeBSD.ORG>, mobile@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pccard pccard.c src/sys/isa sio.c src/sys/dev/ed if_ed_pccard.c src/sys/dev/ep if_ep_pccard.c Message-ID: <199912021618.JAA05518@mt.sri.com> In-Reply-To: <199912020555.WAA00484@harmony.village.org> References: <199912020539.VAA00927@mass.cdrom.com> <199912020555.WAA00484@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> : This actually becomes much more complex when you bring CardBus into the > : picture, as I believe (correct me if I'm wrong, since you have the spec > : there) that it uses level-triggered interrupts. In this case, the device > : interrupt handler can't return (well, it can, but it will be immediately > : re-entered). > > Yes. Both cardbus and pccard use level triggered interrupts (or can > use level triggered interrupts). But if the card goes away, the > bridge, I believe, deasserts the interrupt for the card. I don't believe this is the case, at least for PCMCIA (from experience). Nate > : Oh, and I forgot with the CardBus thing above; if the slot is sharing an > : interrupt with someone else, you're probably screwed as well. (Unless the > : bus lets you call back into it to disable a slot once you've detected > : that it's gone.) > > I believe that it is common practice to share the cardbus card > interrupt with the cardbus bridge, but I may be mistaken about that. Does the bridge need an interrupt? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912021618.JAA05518>