Date: Tue, 26 Oct 1999 20:02:14 -0600 From: Nate Williams <nate@mt.sri.com> To: Terry Lambert <tlambert@primenet.com> Cc: nate@mt.sri.com, rjesup@wgate.com, imp@village.org, arch@freebsd.org Subject: Re: Racing interrupts Message-ID: <199910270202.UAA21309@mt.sri.com> In-Reply-To: <199910270140.SAA16700@usr02.primenet.com> References: <199910261525.JAA18872@mt.sri.com> <199910270140.SAA16700@usr02.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Such as? Of course, just because the MS spec says you should be > > > able to pop out the hardware at any time doesn't mean you can't make > > > software that says "you MUST shut down the driver before removing the card > > > or you may lose all your work", but the problem with that is that it breaks > > > the user's expectations, especially if all the other vendors handle it. > > > Not to mention that it's a bad idea from a CHI standpoint. > > > > You're missing the point. What happens if I'm in the middle of a ISR > > when the device is popped out? > > > You get a higher priority device eject interrupt, and abort the device > ISR before exiting the higher priority interrupt routine. You simply don't get it, no matter how many times I've said it. I refuse to repeat myself over and over simply because you are unable to read what I've wrote. Most of your arguments are based on faulty assumptions, which have been pointed out over and over. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910270202.UAA21309>