linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Garcia <jpgarcia@execpc.com>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: Re: sound sleep (more)
Date: Sun, 19 Sep 1999 12:18:35 -0500	[thread overview]
Message-ID: <37E51AEB.AFE383E0@execpc.com> (raw)
In-Reply-To: 37E51662.8ACADA16@execpc.com


i forgot to add that i wrote the i/o interrupt handler code as a side thing
while trying to debug the sound not waking up.  The thing it helped me determine
is that the interrupts are still produced after sound disappears.  so the system
is still there.  sound is produced after a sleep if the module is
removed/slept/isntalled, but not if it is installed while sleeping.   so is the
sound system handled by the PMU always or just when powered up?  is it powered
up only when the module is installed?  If the PMU always handles sound upon
sleeping, why does it work when the module isn't installed at sleep?  any way to
check this further?

more questions i cant answer.

-- 
Joseph P. Garcia      jpgarcia@execpc.com      jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate                      Student Employee - Systems Programmer
University of Wisconsin - Madison                            UW Lidar Group

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-19 17:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-19  8:54 patches: MacOS-like Wallstreet sound in/out controls Benjamin Herrenschmidt
1999-09-19 16:15 ` Joseph Garcia
1999-09-19 16:54   ` Shaw Terwilliger
1999-09-19 16:59     ` sound sleep Joseph Garcia
1999-09-19 17:18       ` Joseph Garcia [this message]
1999-09-20  2:17       ` Takashi Oe
1999-09-20 22:24         ` Joseph Garcia

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=37E51AEB.AFE383E0@execpc.com \
    --to=jpgarcia@execpc.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).