9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pm in the bitsy
Date: Fri,  1 Jun 2001 12:36:50 -0400	[thread overview]
Message-ID: <20010601163651.E5684199EC@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 475 bytes --]

We haven't finished writing the code to suspend/resume the bitsy yet.
We still have to add the code to all the drivers that will make them power off
the piece of hardware they control and power that back on after resume.
Then we need to write the code that turns off memory and turns it back on
after resume and, finally, we need to write the code that deals with the
power-on entry point.  We have done none of this so I'm not surprised you
have problems.

	Sape


[-- Attachment #2: Type: message/rfc822, Size: 1605 bytes --]

From: F.J.Ballesteros <nemo@gsyc.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] pm in the bitsy
Date: Fri, 1 Jun 2001 16:53:15 +0200
Message-ID: <20010601144450.A35CC19A27@mail.cse.psu.edu>

Hi,

	I think I managed to get it suspended using the
code #undefined in power.c. 
	My only problem is that my ignorance regarding the bitsy
doesn't let me know how to make it resume. It seems that the processor
is no longer waking up (I must power cycle it); that's despite
one line that seems to prepare the on/off button to interrupt the
processor and wake it up again. Any hint, pointer,
or direction? 

thanks

             reply	other threads:[~2001-06-01 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-01 16:36 Sape Mullender [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-01 17:55 forsyth
2001-06-01 17:09 Sape Mullender
2001-06-01 17:00 F.J.Ballesteros
2001-06-01 14:53 F.J.Ballesteros
2001-06-01 14:50 presotto

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=20010601163651.E5684199EC@mail.cse.psu.edu \
    --to=sape@plan9.bell-labs.com \
    --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).