From owner-freebsd-current Thu Dec 2 8:26:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A0B314A0B; Thu, 2 Dec 1999 08:26:49 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-151.skylink.it [194.185.55.151]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id RAA03424; Thu, 2 Dec 1999 17:26:28 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id QAA02574; Thu, 2 Dec 1999 16:33:44 +0100 (CET) (envelope-from hibma@skylink.it) Date: Thu, 2 Dec 1999 16:33:44 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Christopher Masto Cc: Warner Losh , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) In-Reply-To: <19991201123629.A5734@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are other contexts for the same issues anyway. USB has devices > that go away suddenly, and it _is_ designed to be hot-removable, so > people are going to be pulling the plug on network adapters, ZIP > drives, etc. We need drivers that are capable of going away cleanly, > or at least without a panic. If a USB device all of a sudden disappears, in the middle of a transaction for example, the transaction simply fails. This means that all is needed is proper error checking on all functions that return an error. PCMCIA has the problem that the hardware register you are talking to can disappear on the spot, between 2 outb()s. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message