From owner-freebsd-mobile  Thu Oct 23 20:14:52 1997
Return-Path: <owner-freebsd-mobile>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA16598
          for mobile-outgoing; Thu, 23 Oct 1997 20:14:52 -0700 (PDT)
          (envelope-from owner-freebsd-mobile)
Received: from word.smith.net.au (word.smith.net.au [202.0.75.3])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA16590
          for <mobile@freebsd.org>; Thu, 23 Oct 1997 20:14:39 -0700 (PDT)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id MAA00751
	for <mobile@freebsd.org>; Fri, 24 Oct 1997 12:41:11 +0930 (CST)
Message-Id: <199710240311.MAA00751@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: mobile@freebsd.org
Subject: Re: Patches from -current for -stable I'd like to commit after testing 
In-reply-to: Your message of "Thu, 23 Oct 1997 20:57:38 CST."
             <199710240257.UAA18449@rocky.mt.sri.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 24 Oct 1997 12:41:10 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > I think that this isn't realistically achievable; the countercase is 
> > when a card is changed while the system is suspended.  When you come 
> > back up it is not safe to make *any* assumptions about what's in either 
> > slot.
> 
> True, but if you could do a mini-probe (as the current code attempts to
> do), then it should work.  However, somehow things aren't yet 'enough'
> alive when we call the mini-probe, so it doesn't work.

Um, "mini-probe"?  ie. "is what used to be there still there?"

> > Um.  I would be trying to fake a removal on power down, followed by a 
> > faked insertion when we wake back up.
> 
> This is what the code that's enabled by apm_pccard_resume does (sort
> of).  Except that it fakes both remove/insertion at resume time.  The
> bad thing is that it requires that the pccard daemon be running for the
> 'insertion' to be correctly done.

Natch; it has to rummage the database somehow.  How else would you get 
at this information?

> > You might be able to fool the pcic into this if you turn the power to
> > the slots off before you go down, and then back on when you come up
> > again - note that I haven't studied the code yet, so I could be
> > talking out an armpit.
> 
> It seems to work on my box doing that now.  Try enabling the sysctl and
> see what happens on your box.

Hmm, OK.  (saves message, tries it)

Works fine here.  Yay!

mike