From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Longhaul - Disable arbiter
Date: Tue, 8 Aug 2006 17:06:28 -0400 [thread overview]
Message-ID: <20060808210628.GE17618@redhat.com> (raw)
In-Reply-To: <44D8FAC1.4050007@interia.pl>
On Tue, Aug 08, 2006 at 10:57:37PM +0200, Rafał Bilski wrote:
> > The only part about this I don't like is that we now need to add
> > code to do similar things on every possible VIA chipset that
> > could take a C3, and there's quite a few of them, and until
> > we have good coverage...
> >
>
> Would be nice, but I have datasheet only for PLE133.
> Older non VIA chipsets have this port enabled and its address is
> returned by BIOS as PM2 address, or maybe BIOS is enabling.
>
> Coverage is big enough because mainboards with newer chipsets seems
> to have new, C3 capable, CPU's on board.
>
> >
> > We're going to -ENODEV, possibly breaking some setups that it might actually
> > already work on (even if only by chance).
>
> It isn't working for BCR2. Cpufreq is saying that it is, but cpuinfo_cur_freq
> returns max f all the time.
Ok, I'll apply this, and see if I can dig up some of the datasheets
on the older chipsets for completeness.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-08 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 17:12 [PATCH] Longhaul - Disable arbiter Rafał Bilski
2006-08-08 19:58 ` Dave Jones
2006-08-08 20:57 ` Rafał Bilski
2006-08-08 21:06 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 5:51 Rafał Bilski
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=20060808210628.GE17618@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=rafalbilski@interia.pl \
/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