1. 16 4月, 2013 1 次提交
  2. 13 3月, 2013 1 次提交
  3. 28 2月, 2013 1 次提交
  4. 14 2月, 2013 1 次提交
    • A
      burying unused conditionals · d64008a8
      Al Viro 提交于
      __ARCH_WANT_SYS_RT_SIGACTION,
      __ARCH_WANT_SYS_RT_SIGSUSPEND,
      __ARCH_WANT_COMPAT_SYS_RT_SIGSUSPEND,
      __ARCH_WANT_COMPAT_SYS_SCHED_RR_GET_INTERVAL - not used anymore
      CONFIG_GENERIC_{SIGALTSTACK,COMPAT_RT_SIG{ACTION,QUEUEINFO,PENDING,PROCMASK}} -
      can be assumed always set.
      d64008a8
  5. 04 2月, 2013 1 次提交
  6. 20 12月, 2012 1 次提交
  7. 29 11月, 2012 1 次提交
  8. 16 11月, 2012 2 次提交
  9. 09 10月, 2012 1 次提交
  10. 04 10月, 2012 1 次提交
  11. 28 9月, 2012 1 次提交
    • D
      Make most arch asm/module.h files use asm-generic/module.h · 786d35d4
      David Howells 提交于
      Use the mapping of Elf_[SPE]hdr, Elf_Addr, Elf_Sym, Elf_Dyn, Elf_Rel/Rela,
      ELF_R_TYPE() and ELF_R_SYM() to either the 32-bit version or the 64-bit version
      into asm-generic/module.h for all arches bar MIPS.
      
      Also, use the generic definition mod_arch_specific where possible.
      
      To this end, I've defined three new config bools:
      
       (*) HAVE_MOD_ARCH_SPECIFIC
      
           Arches define this if they don't want to use the empty generic
           mod_arch_specific struct.
      
       (*) MODULES_USE_ELF_RELA
      
           Arches define this if their modules can contain RELA records.  This causes
           the Elf_Rela mapping to be emitted and allows apply_relocate_add() to be
           defined by the arch rather than have the core emit an error message.
      
       (*) MODULES_USE_ELF_REL
      
           Arches define this if their modules can contain REL records.  This causes
           the Elf_Rel mapping to be emitted and allows apply_relocate() to be
           defined by the arch rather than have the core emit an error message.
      
      Note that it is possible to allow both REL and RELA records: m68k and mips are
      two arches that do this.
      
      With this, some arch asm/module.h files can be deleted entirely and replaced
      with a generic-y marker in the arch Kbuild file.
      
      Additionally, I have removed the bits from m32r and score that handle the
      unsupported type of relocation record as that's now handled centrally.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Acked-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      786d35d4
  12. 31 7月, 2012 1 次提交
  13. 25 5月, 2012 1 次提交
    • L
      microblaze: Do not select GENERIC_GPIO by default · 59516b07
      Lars-Peter Clausen 提交于
      The microblaze architecture does not provide a native GPIO API implementation
      nor requires GPIOLIB, but still selects GENERIC_GPIO by default. As a result the
      following build error occurs, if GPIOLIB is not selected:
      
      	include/asm-generic/gpio.h: In function 'gpio_get_value_cansleep':
      	include/asm-generic/gpio.h:218: error: implicit declaration of function '__gpio_get_value'
      	include/asm-generic/gpio.h: In function 'gpio_set_value_cansleep':
      	include/asm-generic/gpio.h:224: error: implicit declaration of function '__gpio_set_value'
      
      This patch addresses the issue by not selecting GENERIC_GPIO by default. This
      causes the GPIO API to be stubbed out if no implementation is provided.
      Signed-off-by: NLars-Peter Clausen <lars@metafoo.de>
      Cc: stable@vger.kernel.org
      Tested-by: NMichal Simek <monstr@monstr.eu>
      59516b07
  14. 22 5月, 2012 1 次提交
    • T
      timers: Fixup the Kconfig consolidation fallout · 764e0da1
      Thomas Gleixner 提交于
      Sigh, I missed to check which architecture Kconfig files actually
      include the core Kconfig file. There are a few which did not. So we
      broke them.
      
      Instead of adding the includes to those, we are better off to move the
      include to init/Kconfig like we did already with irqs and others.
      
      This does not change anything for the architectures using the old
      style periodic timer mode. It just solves the build wreckage there.
      
      For those architectures which use the clock events infrastructure it
      moves the include of the core Kconfig file to "General setup" which is
      a way more logical place than having it at random locations specified
      by the architecture specific Kconfigs.
      Reported-by: NIngo Molnar <mingo@kernel.org>
      Cc: Anna-Maria Gleixner <anna-maria@glx-um.de>
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      764e0da1
  15. 21 5月, 2012 1 次提交
  16. 05 5月, 2012 2 次提交
  17. 23 3月, 2012 4 次提交
  18. 16 2月, 2012 1 次提交
  19. 20 1月, 2012 1 次提交
    • D
      microblaze: generic atomic64 support · eacb6ec9
      Daniel Borkmann 提交于
      This tiny patch adds generic atomic64 support for the Microblaze
      architecture.
      
      The patch is against the latest linux-2.6-microblaze tree. It also
      fixes the kernel build for microblaze:
      
      Error log:
      CC kernel/trace/trace_clock.o
      kernel/trace/trace_clock.c:117: error: expected '=', ',', ';', 'asm'
      or '__attribute__' before 'trace_counter'
      kernel/trace/trace_clock.c: In function 'trace_clock_counter':
      kernel/trace/trace_clock.c:126: error: implicit declaration of
      function 'atomic64_add_return'
      kernel/trace/trace_clock.c:126: error: 'trace_counter' undeclared
      (first use in this function)
      kernel/trace/trace_clock.c:126: error: (Each undeclared identifier is
      reported only once
      kernel/trace/trace_clock.c:126: error: for each function it appears in.)
      make[2]: *** [kernel/trace/trace_clock.o] Error 1
      make[1]: *** [kernel/trace] Error 2
      make: *** [kernel] Error 2
      Signed-off-by: NAriane Keller <ariane.keller@tik.ee.ethz.ch>
      Signed-off-by: NDaniel Borkmann <daniel.borkmann@tik.ee.ethz.ch>
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      eacb6ec9
  20. 12 1月, 2012 1 次提交
  21. 29 11月, 2011 1 次提交
    • M
      microblaze: switch to GENERIC_PCI_IOMAP · 1b34d160
      Michael S. Tsirkin 提交于
      microblaze copied pci_iomap from generic code, probably to avoid
      pulling the rest of iomap.c in.  Since that's in
      a separate file now, we can reuse the common implementation.
      
      The only difference is handling of nocache flag,
      that turns out to be done correctly by the
      generic code since arch/microblaze/include/asm/io.h
      defines ioremap_nocache same as ioremap.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      1b34d160
  22. 27 5月, 2011 1 次提交
  23. 14 4月, 2011 1 次提交
  24. 30 3月, 2011 1 次提交
  25. 29 3月, 2011 1 次提交
  26. 24 3月, 2011 1 次提交
  27. 15 3月, 2011 1 次提交
  28. 09 3月, 2011 2 次提交
  29. 21 1月, 2011 2 次提交
  30. 30 12月, 2010 1 次提交
    • S
      of/flattree: Add Kconfig for EARLY_FLATTREE · e6ce1324
      Stephen Neuendorffer 提交于
      The device tree code is now in two pieces: some which can be used generically
      on any platform which selects CONFIG_OF_FLATTREE, and some early which is used
      at boot time on only a few architectures.  This patch segregates the early
      code so that only those architectures which care about it need compile it.
      This also means that some of the requirements in the early code (such as
      a cmd_line variable) that most architectures (e.g. X86) don't provide
      can be ignored.
      Signed-off-by: NStephen Neuendorffer <stephen.neuendorffer@xilinx.com>
      [grant.likely@secretlab.ca: remove extra blank line addition]
      [grant.likely@secretlab.ca: fixed incorrect #ifdef CONFIG_EARLY_FLATTREE check]
      [grant.likely@secretlab.ca: Made OF_EARLY_FLATTREE select instead of depend
                                  on OF_FLATTREE]
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      e6ce1324
  31. 21 10月, 2010 1 次提交
  32. 20 9月, 2010 1 次提交
  33. 04 8月, 2010 1 次提交
    • M
      microblaze: Add KGDB support · 2d5973cb
      Michal Simek 提交于
      Kgdb uses brki r16, 0x18 instruction to call
      low level _debug_exception function which save
      current state to pt_regs and call microblaze_kgdb_break
      function. _debug_exception should be called only from
      the kernel space. User space calling is not supported
      because user application debugging uses different handling.
      
      pt_regs_to_gdb_regs loads additional special registers
      which can't be changed
      
       * Enable KGDB in Kconfig
       * Remove ancient not-tested KGDB support
       * Remove ancient _debug_exception code from entry.S
      
      Only MMU KGDB support is supported.
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      CC: Jason Wessel <jason.wessel@windriver.com>
      CC: John Williams <john.williams@petalogix.com>
      CC: Edgar E. Iglesias <edgar.iglesias@petalogix.com>
      CC: linux-kernel@vger.kernel.org
      Acked-by: NJason Wessel <jason.wessel@windriver.com>
      2d5973cb