1. 15 Feb, 2011 4 commits
    • Greg Ungerer's avatar
      m68knommu: add missing linker __modver section · 81174262
      Greg Ungerer authored
      
      
      Add missing linker section __modver to fix:
      
        LD      vmlinux
      /usr/local/bin/../m68k-uclinux/bin/ld.real: error: no memory region specified for loadable section `__modver'
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      81174262
    • Greg Ungerer's avatar
      m68knommu: fix mis-named variable int set_irq_chip loop · b14769d9
      Greg Ungerer authored
      
      
      Compiling for 68360 targets gives:
      
        CC      arch/m68knommu/platform/68360/ints.o
      arch/m68knommu/platform/68360/ints.c: In function ‘init_IRQ’:
      arch/m68knommu/platform/68360/ints.c:135:16: error: ‘irq’ undeclared (first use in this function)
      arch/m68knommu/platform/68360/ints.c:135:16: note: each undeclared identifier is reported only once for each function it appears in
      
      Fix variable name used.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      b14769d9
    • Greg Ungerer's avatar
      m68knommu: add optimize memmove() function · 982cd252
      Greg Ungerer authored
      Add an m68k/coldfire optimized memmove() function for the m68knommu arch.
      This is the same function as used by m68k. Simple speed tests show this
      is faster once buffers are larger than 4 bytes, and significantly faster
      on much larger buffers (4 times faster above about 100 bytes).
      
      This also goes part of the way to fixing a regression caused by commit
      ea61bc46
      
       ("m68k/m68knommu: merge MMU and
      non-MMU string.h"), which breaks non-coldfire non-mmu builds (which is
      the 68x328 and 68360 families). They currently have no memmove() fucntion
      defined, since there was none in the m68knommu/lib functions.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      982cd252
    • Greg Ungerer's avatar
      m68k: remove arch specific non-optimized memcmp() · f9d693d2
      Greg Ungerer authored
      The m68k arch implements its own memcmp() function. It is not optimized
      in any way (it is the most strait forward coding of memcmp you can get).
      Remove it and use the kernels standard memcmp() implementation.
      
      This also goes part of the way to fixing a regression caused by commit
      ea61bc46
      
       ("m68k/m68knommu: merge MMU and
      non-MMU string.h"), which breaks non-coldfire non-mmu builds (which is
      the 68x328 and 68360 families). They currently have no memcmp() function
      defined, since there is none in the m68knommu/lib functions.
      Signed-off-by: default avatarGreg Ungerer <gerg@uclinux.org>
      Acked-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
      f9d693d2
  2. 07 Feb, 2011 20 commits
  3. 06 Feb, 2011 16 commits