1. 03 Jan, 2007 2 commits
    • Guillaume Chazarain's avatar
      [CPUFREQ] Uninitialized use of cmd.val in... · 76ff28c9
      Guillaume Chazarain authored
      [CPUFREQ] Uninitialized use of cmd.val in arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c:acpi_cpufreq_target()
      
      cmd.val was used uninitialized on the line below.
      Signed-off-by: default avatarGuillaume Chazarain <guichaz@yahoo.fr>
      Acked-by: default avatarVenkatesh Pallipadi <venkatesh.pallipadi@intel.com>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      76ff28c9
    • Rafa Bilski's avatar
      [CPUFREQ] Longhaul - Always guess FSB · 24ebead8
      Rafa Bilski authored
      This is patch that solves Ebox mini PC issue and make
      FSB code more specification compilant. At start guess_fsb
      function is guessing 200MHz FSB too. It is better to
      make it in this way because, thanks to this function, driver
      will fail for bogus FSB values caused by bogus multiplier
      value. For PowerSaver processors we can't depend on Max /
      MinMHzFSB because these values are only used for
      PowerSaver 2.0 and 3.0. Most processors on which Longhaul
      is used are PowerSaver 1.0 only. I'm changing code for older
      CPU's too, but not so much as previously, and this code was
      already used for Ezra. Using MinMHzBR for Ezra-T is outside
      spec. It is for voltage scaling purpose and don't have to
      be equal to minmult (but it is). Same for Nehemiah (it
      isn't for sure). Added mult - current multiplier value.
      Signed-off-by: default avatarRafa³ Bilski <rafalbilski@interia.pl>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      24ebead8
  2. 29 Dec, 2006 2 commits
    • Rafa Bilski's avatar
      [CPUFREQ] Longhaul - Fix up powersaver assumptions. · 264166e6
      Rafa Bilski authored
      ACPI PM2 register was fallback for "Longhaul ver. 1" CPU's.
      My assumption that this register isn't present at
      "PowerSaver" motherboards is so far true, but current code
      will not work correctly in other case. There are three possible
      supports: ACPI C3, PM2 and northbridge. That was my assumption
      that ACPI C3 and northbridge is for PS and northbridge and PM2
      is for V1. In current code we can only check if it is ACPI
      support or not by port22_en. So remove port22_en and add
      longhaul_flags. If USE_ACPI_C3 and USE_NORTHBRIDGE are both
      clear then it means ACPI PM2 support. Also change order of
      support probe from ACPI C3, PM2, northbridge to ACPI C3,
      northbridge, ACPI PM2. Paranoid protection against port 0x22
      cast as ACPI PM2 register. Bit 1 clear in such case - lockup
      on AGP DMA. And obvious (now) fixup for do_powersaver. Use
      cx->address only for ACPI C3 ("PowerSaver" processor using
      PM2 support).
      Signed-off-by: default avatarRafa Bilski <rafalbilski@interia.pl>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      264166e6
    • Dave Jones's avatar
      1cfe2014
  3. 23 Dec, 2006 3 commits
  4. 18 Dec, 2006 2 commits
  5. 17 Dec, 2006 1 commit
  6. 13 Dec, 2006 7 commits
  7. 12 Dec, 2006 23 commits