From: Joseph Garcia <jpgarcia@execpc.com>
To: Derek Homeier <supas100@astrophysik.uni-kiel.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: switching consoles
Date: Tue, 18 Jul 2000 16:22:01 -0500 [thread overview]
Message-ID: <3974CA79.C5F0AB2B@execpc.com> (raw)
In-Reply-To: Pine.SOL.3.95.1000718225607.3933D-100000@juliet
Derek Homeier wrote:
> However, this might also be a side effect of writing evil things to the PMU,
> because the crashes were all related to not being able to power on the
> backlight and wake up from sleep mode. Does the PMU handle the ADB stuff as
> well (think I heard so, but not positive)?
i'd think that it would be more likely the nvram resetting. But PMU is actually
on ADB. as far as i know, all direct pmu ioctls (battery query, etc) are sent
to /dev/adb, while interpreted ioctls (like sleep) are sent to /dev/pmu, which
is why /dev/pmu features need kernel support and vary from system to system.
The noodle-scratcher in this is the fact that the keyboard's F-key setting is
maintained post-sleep, while trackpad tapping is always reset. both being ADB
devs reset upon wake, id think it would get reset. there could be something we
are missing.
--
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/
next prev parent reply other threads:[~2000-07-18 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 17:33 switching consoles Derek Homeier
2000-07-14 18:19 ` Joseph Garcia
2000-07-18 20:29 ` Derek Homeier
2000-07-18 20:41 ` Joseph Garcia
2000-07-18 21:13 ` Derek Homeier
2000-07-18 21:22 ` Joseph Garcia [this message]
2000-07-18 21:50 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2000-07-14 9:29 Iain Sandoe
2000-07-14 10:24 ` Martin Costabel
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=3974CA79.C5F0AB2B@execpc.com \
--to=jpgarcia@execpc.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=supas100@astrophysik.uni-kiel.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.