Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Oct 1997 20:57:38 -0600 (MDT)
From:      Nate Williams <nate@mt.sri.com>
To:        Mike Smith <mike@smith.net.au>
Cc:        Nate Williams <nate@mt.sri.com>, mobile@freebsd.org
Subject:   Re: Patches from -current for -stable I'd like to commit after testing 
Message-ID:  <199710240257.UAA18449@rocky.mt.sri.com>
In-Reply-To: <199710240226.LAA00527@word.smith.net.au>
References:  <199710240004.SAA17893@rocky.mt.sri.com> <199710240226.LAA00527@word.smith.net.au>

next in thread | previous in thread | raw e-mail | index | archive | help
> > Unfortunately, they didn't work out.  I was hoping to get suspend/resume
> > to work without requiring the pccard daemon running.  (Ie; once a driver
> > was 'mapped' in, suspend/resume didn't require the daemon to re-register
> > the device, which is how the apm_pccard_resume code from PAO works.)
> 
> 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.

> > In any case, I'd like to figure out a way to have a device truly
> > 'shutdown', and then come back up.  However, I need to look at things a
> > bit more closely, since my 'brute force and ignorance' patch didn't seem
> > to help.
> 
> 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.

> 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.



Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710240257.UAA18449>