1. 24 11月, 2009 1 次提交
  2. 11 7月, 2009 1 次提交
  3. 12 3月, 2009 1 次提交
  4. 06 9月, 2008 2 次提交
  5. 05 9月, 2008 2 次提交
  6. 20 8月, 2008 1 次提交
    • S
      x86: fix "kernel won't boot on a Cyrix MediaGXm (Geode)" · c6744955
      Samuel Sieb 提交于
      Cyrix MediaGXm/Cx5530 Unicorn Revision 1.19.3B has stopped
      booting starting at v2.6.22.
      
      The reason is this commit:
      
      > commit f25f64ed
      > Author: Juergen Beisert <juergen@kreuzholzen.de>
      > Date:   Sun Jul 22 11:12:38 2007 +0200
      >
      >     x86: Replace NSC/Cyrix specific chipset access macros by inlined functions.
      
      this commit activated a macro which was dormant before due to (buggy)
      macro side-effects.
      
      I've looked through various datasheets and found that the GXm and GXLV
      Geode processors don't have an incrementor.
      
      Remove the incrementor setup entirely.  As the incrementor value
      differs according to clock speed and we would hope that the BIOS
      configures it correctly, it is probably the right solution.
      
      Cc: <stable@kernel.org>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      c6744955
  7. 22 7月, 2008 1 次提交
  8. 17 4月, 2008 3 次提交
  9. 07 2月, 2008 1 次提交
    • A
      calibrate_delay() must be __cpuinit · 6c81c32f
      Adrian Bunk 提交于
      calibrate_delay() must be __cpuinit, not __{dev,}init.
      
      I've verified that this is correct for all users.
      
      While doing the latter, I also did the following cleanups:
      - remove pointless additional prototypes in C files
      - ensure all users #include <linux/delay.h>
      
      This fixes the following section mismatches with CONFIG_HOTPLUG=n,
      CONFIG_HOTPLUG_CPU=y:
      
      WARNING: vmlinux.o(.text+0x1128d): Section mismatch: reference to .init.text.1:calibrate_delay (between 'check_cx686_slop' and 'set_cx86_reorder')
      WARNING: vmlinux.o(.text+0x25102): Section mismatch: reference to .init.text.1:calibrate_delay (between 'smp_callin' and 'cpu_coregroup_map')
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Christian Zankel <chris@zankel.net>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6c81c32f
  10. 30 1月, 2008 1 次提交
  11. 20 10月, 2007 3 次提交
  12. 11 10月, 2007 1 次提交
  13. 23 7月, 2007 1 次提交
    • J
      x86: Replace NSC/Cyrix specific chipset access macros by inlined functions. · f25f64ed
      Juergen Beisert 提交于
      Due to index register access ordering problems, when using macros a line
      like this fails (and does nothing):
      
      	setCx86(CX86_CCR2, getCx86(CX86_CCR2) | 0x88);
      
      With inlined functions this line will work as expected.
      
      Note about a side effect: Seems on Geode GX1 based systems the
      "suspend on halt power saving feature" was never enabled due to this
      wrong macro expansion. With inlined functions it will be enabled, but
      this will stop the TSC when the CPU runs into a HLT instruction.
      Kernel output something like this:
      	Clocksource tsc unstable (delta = -472746897 ns)
      
      This is the 3rd version of this patch.
      
       - Adding missed arch/i386/kernel/cpu/mtrr/state.c
      	Thanks to Andres Salomon
       - Adding some big fat comments into the new header file
       	Suggested by Andi Kleen
      
      AK: fixed x86-64 compilation
      Signed-off-by: NJuergen Beisert <juergen@kreuzholzen.de>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      f25f64ed
  14. 22 5月, 2007 1 次提交
    • A
      Detach sched.h from mm.h · e8edc6e0
      Alexey Dobriyan 提交于
      First thing mm.h does is including sched.h solely for can_do_mlock() inline
      function which has "current" dereference inside. By dealing with can_do_mlock()
      mm.h can be detached from sched.h which is good. See below, why.
      
      This patch
      a) removes unconditional inclusion of sched.h from mm.h
      b) makes can_do_mlock() normal function in mm/mlock.c
      c) exports can_do_mlock() to not break compilation
      d) adds sched.h inclusions back to files that were getting it indirectly.
      e) adds less bloated headers to some files (asm/signal.h, jiffies.h) that were
         getting them indirectly
      
      Net result is:
      a) mm.h users would get less code to open, read, preprocess, parse, ... if
         they don't need sched.h
      b) sched.h stops being dependency for significant number of files:
         on x86_64 allmodconfig touching sched.h results in recompile of 4083 files,
         after patch it's only 3744 (-8.3%).
      
      Cross-compile tested on
      
      	all arm defconfigs, all mips defconfigs, all powerpc defconfigs,
      	alpha alpha-up
      	arm
      	i386 i386-up i386-defconfig i386-allnoconfig
      	ia64 ia64-up
      	m68k
      	mips
      	parisc parisc-up
      	powerpc powerpc-up
      	s390 s390-up
      	sparc sparc-up
      	sparc64 sparc64-up
      	um-x86_64
      	x86_64 x86_64-up x86_64-defconfig x86_64-allnoconfig
      
      as well as my two usual configs.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e8edc6e0
  15. 03 5月, 2007 3 次提交
    • T
      [PATCH] i386: Don't delete cpu_devs data to identify different x86 types in late_initcall · 35060b6a
      Thomas Renninger 提交于
      In arch/i386/cpu/common.c there is:
      cpu_devs[X86_VENDOR_INTEL]
      cpu_devs[X86_VENDOR_CYRIX]
      cpu_devs[X86_VENDOR_AMD]
      ...
      They are all filled with data early.
      The data (struct) got set to NULL  for all, but Intel in different
      late_initcall (exit_cpu_vendor) calls.
      I don't see what sense this makes at all, maybe something that got
      forgotten with the HOTPLUG_CPU extenstions?
      
      Please check/review whether initdata, cpuinitdata is still ok and this
      still works with HOTPLUG_CPU and without, it should...
      Signed-off-by: NThomas Renninger <trenn@suse.de>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Cc: davej@redhat.com
      35060b6a
    • J
      [PATCH] x86: Log reason why TSC was marked unstable · 5a90cf20
      john stultz 提交于
      Change mark_tsc_unstable() so it takes a string argument, which holds the
      reason the TSC was marked unstable.
      
      This is then displayed the first time mark_tsc_unstable is called.
      
      This should help us better debug why the TSC was marked unstable on certain
      systems and allow us to make sure we're not being overly paranoid when
      throwing out this troublesome clocksource.
      
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Andi Kleen <ak@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      5a90cf20
    • T
      [PATCH] i386: pit_latch_buggy has no effect · f5e88615
      takada 提交于
      Eliminated the arch/i386/kernel/timers in 2.6.18, use clocksoures instead.
      pit_latch_buggy was referred in timers/timer_tsc.c, and currently removed.
      Therefore nobody refer it.
      
      Until 2.6.17, MediaGX's TSC works correctly.  after 2.6.18, warned "TSC
      appears to be running slowly.  Marking it as unstable".  So marked unstable
      TSC when CS55x0.
      
      Cc: Andi Kleen <ak@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      f5e88615
  16. 13 2月, 2007 3 次提交
    • A
      [PATCH] i386: Fix Cyrix MediaGX detection · 120fad72
      Alan 提交于
      The old Cyrix 5520 CPU detection code relied upon the PCI layer setup being
      done earlier than the CPU setup, which is no longer true.  Fortunately we
      know that if the processor is a MediaGX we can do type 1 pci config
      accesses to check the companion chip.  We thus do those directly and from
      this find the 5520 and implement the workarounds for the timer problem
      
      Original report from takada@mbf.nifty.com, I sent a proposed patch which
      Takara then corrected, tested and sent back to the list on 10th January.
      
      Submitting for merging as it seems to have been missed
      
      AK: Changed to use pci-direct.h and fix warning for !CONFIG_PCI (later
      AK: originally from akpm)
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      Cc: Andi Kleen <ak@suse.de>
      Cc: <takada@mbf.nifty.com>
      Cc: Jordan Crouse <jordan.crouse@amd.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      120fad72
    • T
      [PATCH] i386: geode configuration fixes · bcde1ebb
      TAKADA Yoshihito 提交于
      Original code doesn't write back to CCR4 register.  This patch reflects a
      value of a register.
      
      Cc: Jordan Crouse <jordan.crouse@amd.com>
      Acked-by: NAlan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Andi Kleen <ak@suse.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      bcde1ebb
    • T
      [PATCH] i386: support Classic MediaGXm · 2632f01a
      takada 提交于
      I hope to support "classic" MediaGXm in kernel.
      
      The DIR1 register of MediaGXm( or Geode) shows the following values for
      identify CPU.  For example, My MediaGXm shows 0x42.
      
      We can read National Semiconductor's datasheet without any NDAs.
        http://www.national.com/pf/GX/GXLV.html
      
      from datasheets:
      DIR1
      0x30 - 0x33 GXm rev. 1.0 - 2.3
      0x34 - 0x4f GXm rev. 2.4 - 3.x
      0x5x        GXm rev. 5.0 - 5.4
      0x6x        GXLV
      0x7x         (unknow)
      0x8x	    Gx1
      
      In nsc driver of X, accept 0x30 through 0x82. What will 0x7x mean?
      
      Cc: Jordan Crouse <jordan.crouse@amd.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NAndi Kleen <ak@suse.de>
      2632f01a
  17. 03 2月, 2007 1 次提交
  18. 12 1月, 2007 1 次提交
  19. 26 9月, 2006 4 次提交
  20. 27 6月, 2006 1 次提交
  21. 23 6月, 2006 1 次提交
  22. 06 2月, 2006 1 次提交
  23. 07 1月, 2006 1 次提交
  24. 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
  25. 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