All of
 help / color / mirror / Atom feed
From: "Grover, Andrew" <>
To: "Grover,
	Andrew" <>,
	Ka-shu Wong <>
Cc: Nigel Cunningham
	ACPI List
Subject: RE: Re: [Swsusp-devel] ACPI A/C adaptor status not updated upon resume
Date: Fri, 18 Jul 2003 17:01:26 -0700	[thread overview]
Message-ID: <> (raw)

> From: Grover, Andrew 

> Basically, I am at a loss as to why Eric's machine would report the
> wrong thing. Whoever is setting that bit in memory isn't doing it
> properly, for some reason. (There could be a lot of reasons. Eric, you
> might try sticking a printk in the memory read function in
> drivers/acpi/osl.c and seeing that we are doing a read from 0x000EE8FF
> and what the value is.)
> Regards -- Andy
> PS if you're curious the EE8FF is because the SRAM operation region is
> defined as a memory range starting at 0xEE800, and ACST is a field
> offset 0xFF bytes from that.

Or actually the read would be at 0xEE900. Sorry.

Regards -- Andy

This email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here:

             reply	other threads:[~2003-07-19  0:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19  0:01 Grover, Andrew [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-18 23:53 Re: [Swsusp-devel] ACPI A/C adaptor status not updated upon resume Grover, Andrew
     [not found] ` <>
2003-07-19  4:13   ` Ka-shu Wong
     [not found]     ` <>
2003-07-19  4:54       ` Nigel Cunningham
     [not found]         ` <>
2003-07-21  2:31           ` Eric Altendorf
2003-07-17 20:49 Grover, Andrew
     [not found] ` <>
2003-07-18 23:38   ` Ka-shu Wong
     [not found]     ` <>
2003-07-19  1:20       ` Gabor FLEISCHER
     [not found]         ` <>
2003-07-19  3:46           ` Ka-shu Wong

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

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