1. 25 10月, 2011 1 次提交
  2. 18 10月, 2011 6 次提交
    • G
      m68knommu: create common externs for _ram* vars · 7a79a80f
      Greg Ungerer 提交于
      Create common extern definitions of _rambase, _ramstart and _ramend
      instead of them being externed when used in code.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      7a79a80f
    • G
      m68knommu: use generic section names in setup code · c06e9bb4
      Greg Ungerer 提交于
      We should be including and using sections.h to get at the extern
      definitions of the linker sections in the m68knommu startup code.
      Not defining them locally.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      c06e9bb4
    • G
      m68k: merge the mmu and non-mmu traps.c files · 144077ea
      Greg Ungerer 提交于
      The code for handling traps in the non-mmu case is a subset of the mmu
      enabled case. Merge the non-mmu traps_no.c code back to a single traps.c.
      There is actually no code mmu specific here at all, and the processor
      specific code (for the more complex 68020/68030/68040/68060) is already
      proplerly conditionaly used.
      
      The format of console exception dump is a little different, but I don't
      think will cause any one problems, it is purely for debug purposes.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      144077ea
    • G
      m68k: move hardware vector setting from traps.c to its own file · bc4f4ac2
      Greg Ungerer 提交于
      Most of the trap.c code is general to all m68k arch members. But the code
      it currently contains to set the hardware vector table is quite specific to
      the 680x0 family. They can have the vector table at any address unlike
      other family members (which either support only a single fixed address,
      or a limited range of addresses). So lets move that code out to a new file,
      vectors.c. This will make sharing the rest of the trap.c code easier and
      cleaner.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      bc4f4ac2
    • G
      m68k: merge mmu and non-mmu include/asm/entry.h files · 61619b12
      Greg Ungerer 提交于
      The changes in the mmu version of entry.h (entry_mm.h) and the non-mmu
      version (entry_no.h) are not about the presence or use of an MMU at all.
      The main changes are to support the ColdFire processors. The code for
      trap entry and exit for all types of 68k processor outside coldfire is
      the same.
      
      So merge the files back to a single entry.h and share the common 68k
      entry/exit code. Some changes are required for the non-mmu entry
      handlers to adopt the differing macros for system call and interrupt
      entry, but this is quite strait forward. The changes for the ColdFire
      remove a couple of instructions for the separate a7 register case, and
      are no worse for the older single a7 register case.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      61619b12
    • G
      m68k: merge the mmu and non-mmu kernel/Makefiles · 0a01b310
      Greg Ungerer 提交于
      The few differences between the mmu and non-mmu kernel/Makefiles can
      easily be handled inside of a single Makefile. Merge the 2 back into
      a single Makefile.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      Acked-by: NSam Ravnborg <sam@ravnborg.org>
      0a01b310
  3. 27 8月, 2011 1 次提交
  4. 31 7月, 2011 1 次提交
  5. 26 7月, 2011 1 次提交
  6. 25 7月, 2011 3 次提交
  7. 24 7月, 2011 1 次提交
  8. 14 6月, 2011 2 次提交
    • G
      m68k: use kernel processor defines for conditional optimizations · 734c3ce3
      Greg Ungerer 提交于
      Older m68k-linux compilers will include pre-defined symbols that
      confuse what processor it is being targeted for. For example gcc-4.1.2
      will pre-define __mc68020__ even if you specify the target processor
      as -m68000 on the gcc command line. Newer versions of gcc have this
      corrected.
      
      In a few places the m68k code uses defined(__mc68020__) for optimizations
      that include instructions that are specific to the CPU 68020 and above.
      When compiling with older compilers this will be true even when we have
      selected to compile for the older 68000 processors.
      
      Switch to using the kernel processor defines, CONFIG_M68020 and friends.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      734c3ce3
    • G
      m68knommu: fix linker script exported name sections · dab104a7
      Greg Ungerer 提交于
      The recent commit titled "module: Sort exported symbols" (f02e8a65)
      changed the exported symbol name sections. Bring the m68knommu linker
      script into line with those changes - including the sorting of the
      symbol names.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      dab104a7
  9. 29 5月, 2011 1 次提交
    • E
      ns: Wire up the setns system call · 7b21fddd
      Eric W. Biederman 提交于
      32bit and 64bit on x86 are tested and working.  The rest I have looked
      at closely and I can't find any problems.
      
      setns is an easy system call to wire up.  It just takes two ints so I
      don't expect any weird architecture porting problems.
      
      While doing this I have noticed that we have some architectures that are
      very slow to get new system calls.  cris seems to be the slowest where
      the last system calls wired up were preadv and pwritev.  avr32 is weird
      in that recvmmsg was wired up but never declared in unistd.h.  frv is
      behind with perf_event_open being the last syscall wired up.  On h8300
      the last system call wired up was epoll_wait.  On m32r the last system
      call wired up was fallocate.  mn10300 has recvmmsg as the last system
      call wired up.  The rest seem to at least have syncfs wired up which was
      new in the 2.6.39.
      
      v2: Most of the architecture support added by Daniel Lezcano <dlezcano@fr.ibm.com>
      v3: ported to v2.6.36-rc4 by: Eric W. Biederman <ebiederm@xmission.com>
      v4: Moved wiring up of the system call to another patch
      v5: ported to v2.6.39-rc6
      v6: rebased onto parisc-next and net-next to avoid syscall  conflicts.
      v7: ported to Linus's latest post 2.6.39 tree.
      
      >  arch/blackfin/include/asm/unistd.h     |    3 ++-
      >  arch/blackfin/mach-common/entry.S      |    1 +
      Acked-by: NMike Frysinger <vapier@gentoo.org>
      
      Oh - ia64 wiring looks good.
      Acked-by: NTony Luck <tony.luck@intel.com>
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7b21fddd
  10. 24 5月, 2011 12 次提交
  11. 20 5月, 2011 3 次提交
  12. 13 4月, 2011 1 次提交
  13. 31 3月, 2011 1 次提交
  14. 29 3月, 2011 1 次提交
  15. 25 3月, 2011 1 次提交
    • G
      m68k: merge m68k and m68knommu arch directories · 66d857b0
      Greg Ungerer 提交于
      There is a lot of common code that could be shared between the m68k
      and m68knommu arch branches. It makes sense to merge the two branches
      into a single directory structure so that we can more easily share
      that common code.
      
      This is a brute force merge, based on a script from Stephen King
      <sfking@fdwdc.com>, which was originally written by Arnd Bergmann
      <arnd@arndb.de>.
      
      > The script was inspired by the script Sam Ravnborg used to merge the
      > includes from m68knommu. For those files common to both arches but
      > differing in content, the m68k version of the file is renamed to
      > <file>_mm.<ext> and the m68knommu version of the file is moved into the
      > corresponding m68k directory and renamed <file>_no.<ext> and a small
      > wrapper file <file>.<ext> is used to select between the two version. Files
      > that are common to both but don't differ are removed from the m68knommu
      > tree and files and directories that are unique to the m68knommu tree are
      > moved to the m68k tree. Finally, the arch/m68knommu tree is removed.
      >
      > To select between the the versions of the files, the wrapper uses
      >
      > #ifdef CONFIG_MMU
      > #include <file>_mm.<ext>
      > #else
      > #include <file>_no.<ext>
      > #endif
      
      On top of this file merge I have done a simplistic merge of m68k and
      m68knommu Kconfig, which primarily attempts to keep existing options and
      menus in place. Other than a handful of options being moved it produces
      identical .config outputs on m68k and m68knommu targets I tested it on.
      
      With this in place there is now quite a bit of scope for merge cleanups
      in future patches.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      66d857b0
  16. 17 3月, 2011 4 次提交