1. 22 5月, 2012 1 次提交
    • A
      m68k: add TIF_NOTIFY_RESUME and handle it. · a54f1655
      Al Viro 提交于
      TIF_NOTIFY_RESUME added (as bit 5).  That way nommu glue needs no changes at
      all; mmu one needs just to replace jmi do_signal_return to jne do_signal_return
      There we have flags shifted up, until bit 6 (SIGPENDING) is in MSBit; instead
      of checking that MSBit is set (jmi) we check that MSBit or something below it
      is set (jne); bits 0..4 are never set, so that's precisely "bit 6 or bit 5 is
      set".
      
      Usual handling of NOTIFY_RESUME/SIGPENDING is done in do_notify_resume(); glue
      calls it instead of do_signal().
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      a54f1655
  2. 29 3月, 2012 1 次提交
  3. 05 3月, 2012 2 次提交
  4. 18 10月, 2011 2 次提交
    • 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 mmu and non-mmu arch Makefiles · 281eff53
      Greg Ungerer 提交于
      Most of the build logic is the same for the mmu and non-mmu m68k targets.
      Merge the top level architecture Makefiles back into a single Makefile.
      
      For the most part this is just adding the non-mmu processor types and
      their specific cflags and other options into the mmu Makefile.
      
      Note that all the BOARD setting logic that was in the non-mmu Makefile
      is completely removed. It was no longer being used at all.
      
      This has been build and run tested on ColdFire targets and ARAnyM.
      It has been build tested on all the m68k defconfig targets using a
      gcc-4.5.1 based toolchain.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      Acked-by: NSam Ravnborg <sam@ravnborg.org>
      281eff53
  5. 25 7月, 2011 3 次提交
    • G
      m68k: Revive reporting of spurious interrupts · 8c9f08f9
      Geert Uytterhoeven 提交于
      commit 2502b667 ("Change the m68knommu irq
      handling to use the generic irq framework.") removed the reporting of spurious
      interrupts on nommu (68328 and 68360).
      
      Bring it back in a generic way, using "atomic_t irq_err_count", as that's what
      most of the other architectures are using.
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      8c9f08f9
    • G
      m68knommu: correctly use trap_init · 622e9472
      Greg Ungerer 提交于
      Currently trap_init() is an empty function for m68knommu. Instead
      the vectors are being setup as part of the IRQ initialization.
      This is inconsistent with m68k and other architectures.
      
      Change the local init_vectors() to be trap_init(), and init the
      vectors at the correct time during startup. This will help merge of
      m68k and m68knommu trap code in the furture.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      622e9472
    • G
      m68k: merge MMU and non MMU versions of system.h · f941f5ca
      Greg Ungerer 提交于
      The non-MMU m68k targets can use the same asm/system.h as the MMU
      targets. So switch the current system_mm.h to be system.h and remove
      system_no.h.
      
      The assembly support code for the non-MMU resume functions needs to
      be modified to match the now common switch_to() macro. Specifically
      this means correctly saving and restoring the status flags in the case
      of the ColdFire resume, and some reordering of the code to not use
      registers before they are saved or after they are restored.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      f941f5ca
  6. 24 5月, 2011 2 次提交
  7. 29 3月, 2011 1 次提交
  8. 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