Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Pete Popov <ppopov@embeddedalley.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org, cpufreq@www.linux.org.uk
Subject: Re: CPU frequency scaling on MIPS (au1000/common/power.c)
Date: Fri, 24 Sep 2004 22:05:46 +0200	[thread overview]
Message-ID: <20040924200546.GA8033@dominikbrodowski.de> (raw)
In-Reply-To: <20040924183352.31414.qmail@web81407.mail.yahoo.com>

On Fri, Sep 24, 2004 at 11:33:52AM -0700, Pete Popov wrote:
> 
> AMD notified me that the frequency scaling will not be
> supported moving forward and will not be guaranteed to
> work.

... bad for them. Would have been a great feature. But they do have
excellent implementations in other chips...

	Dominik

  reply	other threads:[~2004-09-24 20:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-23 19:48 CPU frequency scaling on MIPS (au1000/common/power.c) Dominik Brodowski
2004-09-23 20:19 ` Pete Popov
2004-09-24 18:33   ` Pete Popov
2004-09-24 20:05     ` Dominik Brodowski [this message]
2004-09-24  8:15 ` Bruno Randolf

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=20040924200546.GA8033@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=ppopov@embeddedalley.com \
    --cc=ralf@linux-mips.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