From owner-freebsd-mobile Fri Oct 24 09:43:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA02669 for mobile-outgoing; Fri, 24 Oct 1997 09:43:50 -0700 (PDT) (envelope-from owner-freebsd-mobile) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA02660 for ; Fri, 24 Oct 1997 09:43:46 -0700 (PDT) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id KAA19149; Fri, 24 Oct 1997 10:43:43 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA20805; Fri, 24 Oct 1997 10:43:42 -0600 (MDT) Date: Fri, 24 Oct 1997 10:43:42 -0600 (MDT) Message-Id: <199710241643.KAA20805@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nate Williams , mobile@freebsd.org Subject: Re: Patches from -current for -stable I'd like to commit after testing In-Reply-To: <199710241634.CAA01177@word.smith.net.au> References: <199710241606.KAA20591@rocky.mt.sri.com> <199710241634.CAA01177@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ Mini-probe ] > Let's just make sure I understand what the 'mini-probe' entails, as I > may be misunderstanding this. > > Before the mini-probe runs, is the device detached? No. It was 'suspended', which basically means the power was pulled from the card slot (and hence the card.) > ie. the mini-probe > is basically going to run the probe and then attach routines again? Just the probe, not the attach. > (Do you have to do this anyway, to get the PCCARD back to a known > state?) Well, there's the issue, and the answer is 'maybe so, I'm not sure'. I don't *think* so, but it may require it. I'm playing with some code to try and not require it. I know the linux code doesn't try to save the state, and instead does what the apm_pccard_resume code does. (Which isn't necessarily a bad thing.) However, I'm not sure what the other OS's do (NetBSD for example). Win95 appears to 'suspend/resume' the card, although it may just be the 'appearances', and not how it's actually implemented under the hood. Nate