1. 27 6月, 2006 1 次提交
  2. 10 4月, 2006 1 次提交
    • J
      [PATCH] x86_64: Fix drift with HPET timer enabled · b20367a6
      Jordan Hargrave 提交于
      If the HPET timer is enabled, the clock can drift by ~3 seconds a day.
      This is due to the HPET timer not being initialized with the correct
      setting (still using PIT count).
      
      If HZ changes, this drift can become even more pronounced.
      
      HPET patch initializes tick_nsec with correct tick_nsec settings for
      HPET timer.
      
      Vojtech comments:
      
        "It's not entirely correct (it assumes the HPET ticks totally
         exactly), but it's significantly better than assuming the PIT error
         there."
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b20367a6
  3. 12 2月, 2006 1 次提交
    • C
      [PATCH] x86-64: Fix HPET timer on x460 · 33042a9f
      Chris McDermott 提交于
      [description from AK]
      
      The IBM Summit 3 chipset doesn't implement the HPET timer replacement
      option.  Since the current Linux code relies on it use a mixed mode with
      both PIT for the interrupt and HPET counters for the time keeping.  That
      was already implemented, but didn't work properly because it was still
      using the last interrupt offset in HPET.  This resulted in x460 not
      booting.  Fix this up by using the free running HPET counter.
      
      Shouldn't affect any other machine because they either use full HPET mode
      or no HPET at all.
      
      TBD needs a similar 32bit fix.
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Cc: Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
      Cc: Bob Picco <bob.picco@hp.com>
      Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
      Cc: john stultz <johnstul@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      33042a9f
  4. 15 11月, 2005 1 次提交
  5. 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