public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Vromans <jvromans@squirrel.nl>
To: "Brown, Len" <len.brown@intel.com>
Cc: Johan Vromans <jvromans@squirrel.nl>,
	Marco Giumelli <mr.giumo@gmail.com>,
	linux-acpi@vger.kernel.org, "Pallipadi,
	Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI
Date: Sat, 28 Jan 2006 16:20:42 +0100	[thread overview]
Message-ID: <m2bqxwjs51.fsf@phoenix.squirrel.nl> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005DD43C6@hdsmsx401.amr.corp.intel.com> (Len Brown's message of "Fri, 27 Jan 2006 14:05:23 -0500")

"Brown, Len" <len.brown@intel.com> writes:

> If I were to hack the DSDT, probably a more interesting thing to do
> would be fill in CPSS with some of the entries from PPSS to give
> your system P-states when on AC power.

What exactly would that provide?

>>http://www.squirrel.nl/people/jvromans/articles/TM4001WLMi/index.html
>
> great job getting your laptop running and sharing your notes
> for others to benefit from your experience!  The only thing
> I didn't notice there was a copy of /proc/cpuinfo

It is, now. Thanks for the suggestion.

-- Johan

  reply	other threads:[~2006-01-28 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27 19:05 UBUNTU - acpi battery on ACER TRAVELMATE 4000 WLMI Brown, Len
2006-01-28 15:20 ` Johan Vromans [this message]
2006-01-30 11:25 ` Bruno Ducrot
  -- strict thread matches above, loose matches on Subject: below --
2006-02-01  2:36 Brown, Len
2006-02-01 10:53 ` Johan Vromans
2006-02-01  2:35 Brown, Len
2006-02-01 23:03 ` Bruno Ducrot
2006-01-26 20:27 Brown, Len
2006-01-27 11:43 ` Johan Vromans
     [not found] <821d061d0601261146j1101d50ew@mail.gmail.com>
2006-01-26 19:52 ` Marco Giumelli
2006-01-27  6:38   ` martin

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=m2bqxwjs51.fsf@phoenix.squirrel.nl \
    --to=jvromans@squirrel.nl \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mr.giumo@gmail.com \
    --cc=venkatesh.pallipadi@intel.com \
    /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