1. 18 12月, 2006 2 次提交
  2. 13 12月, 2006 2 次提交
  3. 28 9月, 2006 1 次提交
  4. 27 9月, 2006 1 次提交
  5. 06 9月, 2006 1 次提交
    • R
      [CPUFREQ] Longhaul - Add voltage scaling to driver · db44aaf3
      Rafa Bilski 提交于
      Rename option "dont_scale_voltage" to "scale_voltage" because
      don't will be default.
      Use "pos" for calculating voltage. In this way driver don't need
      to know mV value or low level value. Simply min U is one pos and
      max U is second pos. All pos between these two are used.
      Assume that min U is for min f and max U for max f. For frequency
      between min and max calculate pos based on difference between
      current frequency and min f.
      Values in mobile VRM table changed to values from
      C3-M datasheet.
      Signed-off-by: NRafa³ Bilski <rafalbilski@interia.pl>
      Signed-off-by: NDave Jones <davej@redhat.com>
      db44aaf3
  6. 14 8月, 2006 1 次提交
  7. 12 8月, 2006 1 次提交
    • R
      [CPUFREQ] Longhaul - Disable arbiter · 179da8e6
      Rafa Bilski 提交于
      ACPI C3 works for "Powersaver" processors, so use it only for them.
      
      Older CPU will change frequency on "halt" only. But we can protect transition
      in two ways:
      - by ACPI PM2 register, there is "bus master arbiter disable" bit.
        This isn't tested because VIA mainboards don't have PM2 register,
      - by PLE133 PCI/AGP arbiter disable register.
        There are two bits in this register. First is "PCI arbiter disable",
        second "AGP arbiter disable". This is working on VIA Epia 800 mainboards.
      
      Test on bm_control is more proper because this is true
      when PM2 register exist.
      Signed-off-by: NRafa³ Bilski <rafalbilski@interia.pl>
      Signed-off-by: NDave Jones <davej@redhat.com>
      179da8e6
  8. 01 8月, 2006 7 次提交
  9. 31 5月, 2006 2 次提交
  10. 05 9月, 2005 1 次提交
    • Z
      [PATCH] i386: inline asm cleanup · 4bb0d3ec
      Zachary Amsden 提交于
      i386 Inline asm cleanup.  Use cr/dr accessor functions.
      
      Also, a potential bugfix.  Also, some CR accessors really should be volatile.
      Reads from CR0 (numeric state may change in an exception handler), writes to
      CR4 (flipping CR4.TSD) and reads from CR2 (page fault) prevent instruction
      re-ordering.  I did not add memory clobber to CR3 / CR4 / CR0 updates, as it
      was not there to begin with, and in no case should kernel memory be clobbered,
      except when doing a TLB flush, which already has memory clobber.
      
      I noticed that page invalidation does not have a memory clobber.  I can't find
      a bug as a result, but there is definitely a potential for a bug here:
      
      #define __flush_tlb_single(addr) \
      	__asm__ __volatile__("invlpg %0": :"m" (*(char *) addr))
      Signed-off-by: NZachary Amsden <zach@vmware.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      4bb0d3ec
  11. 02 9月, 2005 1 次提交
  12. 01 6月, 2005 3 次提交
  13. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4