From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: cpufreq/linux/arch/arm/mach-sa1100 cpu-sa1100.c, 1.5,
Date: Mon, 30 Aug 2004 17:01:07 +0200 [thread overview]
Message-ID: <20040830150107.GA7953@dominikbrodowski.de> (raw)
In-Reply-To: <20040830144940.GS29560@poupinou.org>
On Mon, Aug 30, 2004 at 04:49:40PM +0200, Bruno Ducrot wrote:
> Hi,
>
> On Mon, Aug 30, 2004 at 03:17:25PM +0200, Dominik Brodowski wrote:
> > i386 can adapt to "hidden" changes of CPU frequencies quite well now, as the
> > TSC code tries to detect "changes behind its back"... so these flags were
> > not added out of concern for the x86 architecture, but because they seemed
> > necessary for certain systems. Possibly I'm completely wrong, though...
> >
>
> Well, for a strange reason, I was thinking all those stuff were made for
> speedstep-ich and the (non)-merged speedstep-piix4, and maybe the
> ownership stuff from ACPI.. I was mistaken I guess.
The detection of changes behind cpufreq's back yes -- but for the
speedstep-ich case, it was supposed to work around critical situations, not
to cause panics... If you see a valid point for the PANIC flag for these
drivers, please explain it to me, though.
Thanks,
Dominik
next prev parent reply other threads:[~2004-08-30 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-29 12:49 cpufreq/linux/arch/arm/mach-sa1100 cpu-sa1100.c, 1.5, Dominik Brodowski
2004-08-30 12:19 ` Bruno Ducrot
2004-08-30 13:17 ` Dominik Brodowski
2004-08-30 14:49 ` Bruno Ducrot
2004-08-30 15:01 ` Dominik Brodowski [this message]
2004-08-30 15:16 ` Bruno Ducrot
2004-08-30 16:03 ` Dominik Brodowski
2004-08-30 14:29 ` Russell King
2004-08-30 15:08 ` Dominik Brodowski
2004-08-30 16:16 ` Russell King
2004-08-31 22:23 ` Dave Jones
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=20040830150107.GA7953@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.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