cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Wander Winkelhorst <w.winkelhorst@gmail.com>,
	David Johnson <dj@david-web.co.uk>,
	linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: Re: cpufreq longhaul locks up
Date: Sat, 05 May 2007 23:32:40 +0200	[thread overview]
Message-ID: <463CF7F8.7080007@interia.pl> (raw)
In-Reply-To: <Pine.LNX.4.61.0705052237580.18504@yvahk01.tjqt.qr>

Is patch attached below making things better?
You should see in log that You are using VT8235 support now.

---
 arch/i386/kernel/cpu/cpufreq/longhaul.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/arch/i386/kernel/cpu/cpufreq/longhaul.c b/arch/i386/kernel/cpu/cpufreq/longhaul.c
index 5548e5b..c3c9096 100644
--- a/arch/i386/kernel/cpu/cpufreq/longhaul.c
+++ b/arch/i386/kernel/cpu/cpufreq/longhaul.c
@@ -635,6 +635,8 @@ static int longhaul_setup_vt8235(void)
 
 	/* Find VT8235 southbridge */
 	dev = pci_find_device(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8235, NULL);
+	if (dev == NULL)
+		dev = pci_find_device(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8237, NULL);
 	if (dev != NULL) {
 		/* Set transition time to max */
 		pci_read_config_byte(dev, 0xec, &pci_cmd);
@@ -771,11 +773,11 @@ static int __init longhaul_cpu_init(struct cpufreq_policy *policy)
 		}
 	}
 	/* Check if northbridge is friendly */
-	if (enable_arbiter_disable()) {
+/*	if (enable_arbiter_disable()) {
 		longhaul_flags |= USE_NORTHBRIDGE;
 		goto print_support_type;
 	}
-	/* Use VT8235 southbridge if present */
+*/	/* Use VT8235 southbridge if present */
 	if (longhaul_version == TYPE_POWERSAVER && vt8235_present) {
 		longhaul_flags |= USE_VT8235;
 		goto print_support_type;
-- 



----------------------------------------------------------------------
Wicie, rozumicie....
Zobacz >>> http://link.interia.pl/f1a74

  reply	other threads:[~2007-05-05 21:32 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-04 10:16 cpufreq longhaul locks up Jan Engelhardt
2007-05-04 11:36 ` Wander Winkelhorst
2007-05-04 11:51   ` Jan Engelhardt
2007-05-04 17:08 ` Rafał Bilski
2007-05-04 17:42   ` Chuck Ebbert
2007-05-04 18:40     ` Rafał Bilski
2007-05-04 18:08   ` Wander Winkelhorst
2007-05-04 19:00     ` Rafał Bilski
2007-05-04 18:48   ` Jan Engelhardt
2007-05-04 20:11     ` Rafał Bilski
2007-05-04 21:03       ` Jan Engelhardt
2007-05-04 20:37 ` john stultz
2007-05-04 21:02   ` Jan Engelhardt
2007-05-04 22:49     ` john stultz
2007-05-04 23:32       ` Jan Engelhardt
2007-05-05  4:03         ` Rafał Bilski
2007-05-05  8:00           ` Jan Engelhardt
2007-05-05 13:58             ` Rafał Bilski
2007-05-05 18:13               ` Jan Engelhardt
2007-05-04 22:20 ` David Johnson
2007-05-04 23:37   ` Jan Engelhardt
2007-05-05  5:40     ` Rafał Bilski
2007-05-05  8:44       ` Wander Winkelhorst
2007-05-05 14:02         ` Rafał Bilski
2007-05-05 17:48         ` Rafał Bilski
2007-05-05 18:42           ` Jan Engelhardt
2007-05-05 19:58             ` Rafał Bilski
2007-05-05 20:30               ` Jan Engelhardt
2007-05-05 20:50               ` Jan Engelhardt
2007-05-05 21:32                 ` Rafał Bilski [this message]
2007-05-06  7:53                   ` Jan Engelhardt
2007-05-06  5:12                 ` Rafał Bilski
2007-05-06  8:03                   ` Jan Engelhardt
2007-05-06  9:23                     ` Rafał Bilski
2007-05-06  9:32                       ` Jan Engelhardt
2007-05-06 10:25                         ` Rafał Bilski
2007-05-06 11:33                           ` Jan Engelhardt
2007-05-06 12:20                             ` Rafał Bilski
2007-05-05  9:37       ` Jan Engelhardt
2007-05-05 14:10         ` Rafał Bilski
2007-05-05 17:38           ` Jan Engelhardt
2007-05-05 18:04             ` Rafał Bilski
2007-05-05 18:23               ` Jan Engelhardt

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=463CF7F8.7080007@interia.pl \
    --to=rafalbilski@interia.pl \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=dj@david-web.co.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w.winkelhorst@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox