From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Use information from Longhaul
Date: Mon, 10 Jul 2006 07:45:08 +0200 [thread overview]
Message-ID: <44B1E964.3020001@interia.pl> (raw)
In-Reply-To: <20060709210027.GC10044@redhat.com>
> > I don't know how to explain this properly in English. I will use example.
> > This is from my Nehemiah:
> > min f = 433MHz = 6.5 * 66MHz
> > max f = 999MHz = 7.5 * 133MHz
> > but this is Nehemiah "C" and it is working downto 4.0 multiplier.
> >
> > This is Ezra that I have found in Google (output from Your program):
> > min f = 300MHz = 3.0 * 100MHz
> > max f = 864MHz = 6.5 * 133MHz
>
> But this is only true IFF we scale the FSB, which we don't.
> The above scenarios will not happen for as long as that is true.
>
I'm starting to thinking that printing this information to user
isn't good idea. Probably will cause confusion. What are You thinking
about printing min( longhaul_table[].frequency )? This would print
motherboard, not processor, limit.
Rafa³
----------------------------------------------------------------------
PS. Fajny portal... >>> http://link.interia.pl/f196a
next prev parent reply other threads:[~2006-07-10 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 9:53 [PATCH] Longhaul - Use information from Longhaul Rafał Bilski
2006-07-09 19:00 ` Dave Jones
2006-07-09 19:47 ` Rafał Bilski
2006-07-09 20:08 ` Rafał Bilski
2006-07-09 21:00 ` Dave Jones
2006-07-09 21:45 ` Rafał Bilski
2006-07-10 5:45 ` Rafał Bilski [this message]
2006-07-10 14:28 ` 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=44B1E964.3020001@interia.pl \
--to=rafalbilski@interia.pl \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
/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.