1. 13 7月, 2015 1 次提交
    • G
      m68knommu: force setting of CONFIG_CLOCK_FREQ for ColdFire · d9ee4896
      Greg Ungerer 提交于
      It is possible to disable the clock selection at configuration time,
      but for ColdFire targets we always expect a clock frequency to be
      selected. This results in the following compile time error:
      
        CC      arch/m68k/kernel/asm-offsets.s
      In file included from ./arch/m68k/include/asm/timex.h:14:0,
                       from include/linux/timex.h:65,
                       from include/linux/sched.h:19,
                       from arch/m68k/kernel/asm-offsets.c:14:
      ./arch/m68k/include/asm/coldfire.h:25:2: error: #error "Don't know what your ColdFire CPU clock frequency is??"
      
      Remove CONFIG_CLOCK_SELECT completely and always enable CONFIG_CLOCK_FREQ
      for ColdFire.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      Acked-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      d9ee4896
  2. 15 3月, 2011 7 次提交
    • G
      m68knommu: remove ColdFire CLOCK_DIV config option · ce3de78a
      Greg Ungerer 提交于
      The reality is that you do not need the abiltity to configure the
      clock divider for ColdFire CPUs. It is a fixed ratio on any given
      ColdFire family member. It is not the same for all ColdFire parts,
      but it is always the same in a model range. So hard define the divider
      for each supported ColdFire CPU type and remove the Kconfig option.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      ce3de78a
    • G
      m68knommu: make ColdFire internal peripheral region configurable · d4852a34
      Greg Ungerer 提交于
      Most ColdFire CPUs have an internal peripheral set that can be mapped at
      a user selectable address. Different ColdFire parts either use an MBAR
      register of an IPSBAR register to map the peripheral region. Most boards
      use the Freescale default mappings - but not all.
      
      Make the setting of the MBAR or IPSBAR register configurable. And only make
      the selection available on the appropriate ColdFire CPU types.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      d4852a34
    • G
      m68knommu: clean up definitions of ColdFire peripheral base registers · b195c479
      Greg Ungerer 提交于
      Different ColdFire CPUs have different ways of defining where their
      internal peripheral registers sit in their address space. Some use an
      MBAR register, some use and IPSBAR register, some have a fixed mapping.
      
      Now that most of the peripheral address definitions have been cleaned up
      we can clean up the setting of the MBAR and IPSBAR defines to limit them
      to just where they are needed (and where they actually exist).
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      b195c479
    • G
      m68knommu: remove MBAR and IPSBAR hacks for the ColdFire 520x CPUs · 571f0608
      Greg Ungerer 提交于
      The ColdFire 5207 and 5208 CPUs have fixed peripheral addresses.
      They do not use the setable peripheral address registers like the MBAR
      and IPSBAR used on many other ColdFire parts. Don't use fake values
      of MBAR and IPSBAR when using peripheral addresses for them, there
      is no need to.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      571f0608
    • G
      m68knommu: remove bogus definition of MBAR for ColdFire 532x family · cdfc243e
      Greg Ungerer 提交于
      Remove the bogus definition of the MBAR register for the ColdFire 532x
      family. It doesn't have an MBAR register, its peripheral registers are
      at fixed addresses and are not relative to a settable base.
      
      All the code that relyed on this definition existing has been cleaned
      up. The register address definitions now include the base as required.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      cdfc243e
    • G
      m68knommu: remove kludge seting of MCF_IPSBAR for ColdFire 54xx · 254eef74
      Greg Ungerer 提交于
      The ColdFire 54xx family shares the same interrupt controller used
      on the 523x, 527x and 528x ColdFire parts, but it isn't offset
      relative to the IPSBAR register. The 54xx doesn't have an IPSBAR
      register.
      
      By including the base address of the peripheral registers in the register
      definitions (MCFICM_INTC0 and MCFICM_INTC1 in this case) we can avoid
      having to define a fake IPSBAR for the 54xx. And this makes the register
      address definitions of these more consistent, the majority of the other
      register address defines include the peripheral base address already.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      254eef74
    • G
      m68knommu: move ColdFire 5249 MBAR2 definition · f2ba710d
      Greg Ungerer 提交于
      The MBAR2 register is only used on the ColdFire 5249 part, so move its
      definition out of the common coldfire.h and into the 5249 support header.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      f2ba710d
  3. 05 1月, 2011 1 次提交
    • G
      m68knommu: make Coldfire 548x support more generic · 5b2e6555
      Greg Ungerer 提交于
      The ColdFire 547x family of processors is very similar to the ColdFire
      548x series. Almost all of the support for them is the same. Make the
      code supporting the 548x more gneric, so it will be capable of
      supporting both families.
      
      For the most part this is a renaming excerise to make the support
      code more obviously apply to both families.
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      5b2e6555
  4. 21 10月, 2010 1 次提交
  5. 16 1月, 2009 1 次提交
    • S
      m68k,m68knommu: merge header files · 49148020
      Sam Ravnborg 提交于
      Merge header files for m68k and m68knommu to the single location:
      
          arch/m68k/include/asm
      
      The majority of this patch was the result of the
      script that is included in the changelog below.
      
      The script was originally written by Arnd Bergman and
      exten by me to cover a few more files.
      
      When the header files differed the script uses the following:
      
      The original m68k file is named <file>_mm.h  [mm for memory manager]
      The m68knommu file is named <file>_no.h [no for no memory manager]
      
      The files uses the following include guard:
      
      This include gaurd works as the m68knommu toolchain set
      the __uClinux__ symbol - so this should work in userspace too.
      
      Merging the header files for m68k and m68knommu exposes the
      (unexpected?) ABI differences thus it is easier to actually
      identify these and thus to fix them.
      
      The commit has been build tested with both a m68k and
      a m68knommu toolchain - with success.
      
      The commit has also been tested with "make headers_check"
      and this patch fixes make headers_check for m68knommu.
      
      The script used:
      TARGET=arch/m68k/include/asm
      SOURCE=arch/m68knommu/include/asm
      
      INCLUDE="cachectl.h errno.h fcntl.h hwtest.h ioctls.h ipcbuf.h \
      linkage.h math-emu.h md.h mman.h movs.h msgbuf.h openprom.h \
      oplib.h poll.h posix_types.h resource.h rtc.h sembuf.h shmbuf.h \
      shm.h shmparam.h socket.h sockios.h spinlock.h statfs.h stat.h \
      termbits.h termios.h tlb.h types.h user.h"
      
      EQUAL="auxvec.h cputime.h device.h emergency-restart.h futex.h \
      ioctl.h irq_regs.h kdebug.h local.h mutex.h percpu.h \
      sections.h topology.h"
      
      NOMUUFILES="anchor.h bootstd.h coldfire.h commproc.h dbg.h \
      elia.h flat.h m5206sim.h m520xsim.h m523xsim.h m5249sim.h \
      m5272sim.h m527xsim.h m528xsim.h m5307sim.h m532xsim.h \
      m5407sim.h m68360_enet.h m68360.h m68360_pram.h m68360_quicc.h \
      m68360_regs.h MC68328.h MC68332.h MC68EZ328.h MC68VZ328.h \
      mcfcache.h mcfdma.h mcfmbus.h mcfne.h mcfpci.h mcfpit.h \
      mcfsim.h mcfsmc.h mcftimer.h mcfuart.h mcfwdebug.h \
      nettel.h quicc_simple.h smp.h"
      
      FILES="atomic.h bitops.h bootinfo.h bug.h bugs.h byteorder.h cache.h \
      cacheflush.h checksum.h current.h delay.h div64.h \
      dma-mapping.h dma.h elf.h entry.h fb.h fpu.h hardirq.h hw_irq.h io.h \
      irq.h kmap_types.h machdep.h mc146818rtc.h mmu.h mmu_context.h \
      module.h page.h page_offset.h param.h pci.h pgalloc.h \
      pgtable.h processor.h ptrace.h scatterlist.h segment.h \
      setup.h sigcontext.h siginfo.h signal.h string.h system.h swab.h \
      thread_info.h timex.h tlbflush.h traps.h uaccess.h ucontext.h \
      unaligned.h unistd.h"
      
      mergefile() {
      	BASE=${1%.h}
      	git mv ${SOURCE}/$1 ${TARGET}/${BASE}_no.h
      	git mv ${TARGET}/$1 ${TARGET}/${BASE}_mm.h
      
      cat << EOF > ${TARGET}/$1
      EOF
      
      	git add ${TARGET}/$1
      }
      
      set -e
      
      mkdir -p ${TARGET}
      
      git mv include/asm-m68k/* ${TARGET}
      rmdir include/asm-m68k
      
      git rm ${SOURCE}/Kbuild
      for F in $INCLUDE $EQUAL; do
      	git rm ${SOURCE}/$F
      done
      
      for F in $NOMUUFILES; do
      	git mv ${SOURCE}/$F ${TARGET}/$F
      done
      
      for F in $FILES ; do
      	mergefile $F
      done
      
      rmdir arch/m68knommu/include/asm
      rmdir arch/m68knommu/include
      
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      49148020
  6. 07 8月, 2008 1 次提交
  7. 26 6月, 2006 1 次提交
  8. 26 4月, 2006 1 次提交
  9. 02 11月, 2005 1 次提交
  10. 09 9月, 2005 1 次提交
  11. 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