cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Alexey Starikovskiy <alexey_y_starikovskiy@linux.intel.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Pentium D 915 support
Date: Thu, 03 Aug 2006 18:37:23 +0200	[thread overview]
Message-ID: <1154623044.4302.550.camel@queen.suse.de> (raw)
In-Reply-To: <44D21666.5030304@linux.intel.com>

> Thomas Renninger wrote:
> > available frequency steps: 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80
> > GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.80 GHz, 2.40 GHz
> > 
> Algorithm does not care about same P-steps. It will get to 2.4 in one step.
> This is not BIOS bug, it is just a way to avoid dynamic memory allocation in BIOS.
> And it has nothing to do with performance losses due to note above.

That makes sense, thanks for pointing that out,

    Thomas

  parent reply	other threads:[~2006-08-03 16:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 13:12 Pentium D 915 support Erik Slagter
2006-07-30 15:33 ` Alexey Starikovskiy
2006-07-30 15:58   ` Erik Slagter
2006-08-03 11:44     ` Thomas Renninger
2006-08-03 11:48       ` Erik Slagter
2006-08-03 14:56         ` Thomas Renninger
2006-08-03 14:55           ` Erik Slagter
2006-08-03 15:29           ` Alexey Starikovskiy
2006-08-03 15:33             ` Erik Slagter
2006-08-03 15:51               ` Alexey Starikovskiy
2006-08-03 16:37             ` Thomas Renninger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03 15:57 Brown, Len
2006-08-03 16:29 ` Erik Slagter

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=1154623044.4302.550.camel@queen.suse.de \
    --to=trenn@suse.de \
    --cc=alexey_y_starikovskiy@linux.intel.com \
    --cc=cpufreq@lists.linux.org.uk \
    /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