From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bitsy suspend/resume (was: ipaq dual pcmcia sleeve)
Date: Wed, 23 Oct 2002 08:48:27 +0200 [thread overview]
Message-ID: <15633b9c82e32464e6e9944d13b4b064@plan9.escet.urjc.es> (raw)
> So, I have a short `window' in which I can resume; if I wait too long,
> I can see the screen, but that seems to be all.
What you say is the behaviour I got before getting the suspend
code working for me. It had to do with some problems
in the power suspend procedure that could broke the ram refresh.
I'll try to get some time today to try a fresh kernel out of
the tar ball, to see if we can get somewhere.
BTW, did you try the tar ball w/o your hacks?
next reply other threads:[~2002-10-23 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 6:48 Fco.J.Ballesteros [this message]
2002-10-23 9:56 ` Axel Belinfante
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 15:57 Fco.J.Ballesteros
2002-10-22 23:20 presotto
2002-10-22 15:01 [9fans] ipaq dual pcmcia sleeve unsupported? (or so it seems) Fco.J.Ballesteros
2002-10-22 21:38 ` [9fans] bitsy suspend/resume (was: ipaq dual pcmcia sleeve) Axel Belinfante
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15633b9c82e32464e6e9944d13b4b064@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).