All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Bilski" <rafalbilski@interia.pl>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: ACPI P-States vs Longhaul
Date: Mon, 20 Nov 2006 20:37:25 +0100	[thread overview]
Message-ID: <456203F5.60606@interia.pl> (raw)

Hello,

I know that a lot has changed since 2.6.18 in "ACPI P-States" 
driver, but I wasn't paing attention. Just in case if this 
issue isn't known. Reported by user. 
System: VIA Epia SP13000 (VIA C3-2 "Nehemiah" 6.9.8)
Kernel: 2.6.18.2 custom config, apci-cpufreq=m, longhaul=m
Issue:
"ACPI P-States driver" is loaded (by distro) and stays loaded. 
When user try to load "Longhaul" CPU is already owned by other 
driver and "Longhaul" fails with -EBUSY. Of course rmmod does 
the trick. But why acpi-cpufreq didn't failed? This processor 
don't support P-states.
Sadly "Longhaul" don't work too. No ACPI C3 support in BIOS 
and CN400 chipset on mainboard.

Regards
Rafa³


----------------------------------------------------------------------
PS. >>> http://link.interia.pl/f19a6

             reply	other threads:[~2006-11-20 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 19:37 Rafał Bilski [this message]
2006-11-20 19:59 ` ACPI P-States vs Longhaul 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=456203F5.60606@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.