cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot@poupinou.org>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@www.linux.org.uk, Dominik Brodowski <linux@brodo.de>
Subject: Re: [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds
Date: Wed, 12 Nov 2003 16:02:45 +0100	[thread overview]
Message-ID: <20031112150245.GA32464@poupinou.org> (raw)
In-Reply-To: <20031112141754.GC31026@redhat.com>

On Wed, Nov 12, 2003 at 02:17:54PM +0000, Dave Jones wrote:
> On Wed, Nov 12, 2003 at 12:01:34PM +0100, Ducrot Bruno wrote:
>  > On Tue, Nov 11, 2003 at 10:45:02PM +0000, Dave Jones wrote:
>  > > On Tue, Nov 11, 2003 at 07:54:17PM +0100, Dominik Brodowski wrote:
>  > >  > BTW, it's not enough for powernow-k7 to divide the BIOS-known latency by 50.
>  > >  > This latency for one VID and one FID transition needs to be multiplied by
>  > >  > the number of p-states minus 1, as that's the actual maximum latency due to
>  > >  > the "one step up/down only" loop, IIRC.
>  > > 
>  > > Yoinks, I thought I had merged that patch (so did you judging from
>  > > that last sentence), but it fell through the cracks somehow.
>  > > I'll see if I can dig it out if I still have it.
>  > > 
>  > > 		Dave
>  > > 
>  > 
>  > I expected that correcting latency and fixing the change_[FV]ID()
>  > will make any patch doing 'one step up/down only' for K7 to be rejected?
> 
> Worse yet, I can't put my finger on the mail that had the patch.
> I'll dig some more, but I'm wondering if this was lost in the
> window between a backup and my IBM deskstars dieing a few months back.
> 

Well, I should have one or two patch(s) for, if really needed,
but what I wanted to point is that now 'latency' is fixed,
and change_VID() is debugged, my brain-damaged try-to-hang

http://www.poupinou.org/cpufreq/test_all_freqs.c

don't want to crash the laptop now.

Cheers,

-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.

  reply	other threads:[~2003-11-12 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 16:08 [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds Dominik Brodowski
2003-11-10 16:32 ` Dave Jones
2003-11-10 17:15   ` Ducrot Bruno
2003-11-10 17:22     ` Dave Jones
2003-11-10 20:50       ` Dominik Brodowski
2003-11-10 21:16         ` Dave Jones
2003-11-11 18:54           ` Dominik Brodowski
2003-11-11 22:45             ` Dave Jones
2003-11-12 11:01               ` Ducrot Bruno
2003-11-12 14:17                 ` Dave Jones
2003-11-12 15:02                   ` Ducrot Bruno [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-11 19:57 Pallipadi, Venkatesh

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=20031112150245.GA32464@poupinou.org \
    --to=ducrot@poupinou.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux@brodo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox