From: Pavel Machek <pavel@ucw.cz>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: linux@dominikbrodowski.de, cpufreq@www.linux.org.uk
Subject: Re: overrides
Date: Wed, 17 Mar 2004 21:08:15 +0100 [thread overview]
Message-ID: <20040317200815.GD287@elf.ucw.cz> (raw)
In-Reply-To: <20040317200051.GS28592@poupinou.org>
On St 17-03-04 21:00:51, Bruno Ducrot wrote:
> On Wed, Mar 17, 2004 at 12:01:49PM -0600, paul.devriendt@amd.com wrote:
> > > -----Original Message-----
> > > From: Bruno Ducrot [mailto:ducrot@poupinou.org]
> > > Sent: Wednesday, March 17, 2004 10:04 AM
> > > To: Pavel Machek
> > > Cc: Dominik Brodowski; Cpufreq mailing list
> > > Subject: Re: powernow-k8, more updates
> > >
> > > Why not just provide an override from userspace?
> >
> > The question of overrides is a difficult question. The
> > theory is that BIOS provides a table of frequencies/
> > voltages that should be used for this system. This is
> > because different processors vary on the frequencies
> > that they support, and different processors have
> > different voltages for the same frequency. Also, the
> > platform may have additional restrictions, such as the
> > need to restrict operation at higher frequencies when
> > running on battery power.
>
> Then I think it's way better to kill all of this overriding stuff.
>
> If people want to override, then they have to reimplemente that
> by themself.
>
> It's pretty easy by now to change that '#if 0' by '#if 1'...
Yes, but please keep it in for now. It should be killed before
mainline merge, but it is very helpfull for me just now.
(Oh, and I think I actually cleaned code up while making overriding
easier.)
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2004-03-17 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 18:01 overrides paul.devriendt
2004-03-17 20:00 ` overrides Bruno Ducrot
2004-03-17 20:08 ` Pavel Machek [this message]
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=20040317200815.GD287@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
--cc=linux@dominikbrodowski.de \
/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 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.