Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 09 11月, 2011 13 次提交
  3. 01 11月, 2011 1 次提交
  5. 25 10月, 2011 3 次提交
  7. 21 10月, 2011 2 次提交
  9. 18 10月, 2011 12 次提交
    • 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: remove extern declarations of memory_start/memory_end from mm/init · 3998bfbf
      由 Greg Ungerer 提交于 
      We do not need to have local extern declarations of memory_start and
memory_end in mm/init_no.c. There are declarations already in asm/page_no.h.
Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      3998bfbf
    • G
      m68knommu: use generic section names in mm/init code · 9da48c01
      由 Greg Ungerer 提交于 
      We should be including and using sections.h to get at the extern
definitions of the linker sections in the m68knommu mm init code.
Not defining them locally.
Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      9da48c01
    • 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
    • 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
    • G
      m68k: reorganize Kconfig options to improve mmu/non-mmu selections · 0e152d80
      由 Greg Ungerer 提交于 
      The current mmu and non-mmu Kconfig files can be merged to form
a more general selection of options. The current break up of options
is due to the simple brute force merge from the m68k and m68knommu
arch directories.

Many of the options are not at all specific to having the MMU enabled
or not. They are actually associated with a particular CPU type or
platform type.

Ultimately as we support all processors with the MMU disabled we need
many of these options to be selectable without the MMU option enabled.
And likewise some of the ColdFire processors, which currently are only
supported with the MMU disabled, do have MMU hardware, and will need
to have options selected on CPU type, not MMU disabled.

This patch removes the old mmu and non-mmu Kconfigs and instead breaks
up the configuration into four areas: cpu, machine, bus, devices.

The Kconfig.cpu lists all the options associated with selecting a CPU,
and includes options specific to each CPU type as well.

Kconfig.machine lists all options associated with selecting a machine
type. Almost always the machines selectable is restricted by the chosen
CPU.

Kconfig.bus contains options associated with selecting bus types on the
various machine types. That includes PCI bus, PCMCIA bus, etc.

Kconfig.devices contains options for drivers and driver associated
options.
Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      0e152d80
    • P
      m68knommu: fix problems with SPI/GPIO on ColdFire 520x · 89127ed3
      由 Peter Turczak 提交于 
      The problem has its root in the calculation of the set-port offsets (macro
MCFGPIO_SETR() in arch/m68k/include/asm/gpio.h), this assumes that all ports
have the same offset from the base port address (MCFGPIO_SETR) which is
defined in mcf520xsim.h as an alias of MCFGIO_PSETR_BUSCTL. Because the BUSCTL
and BE port do not have a set-register (see MCF5208 Reference Manual Page
13-10, Table 13-3) the offset calculations went wrong.

Because the BE and BUSCTL port do not seem useful in these parts, as they
lack a set register, I removed them and adapted the gpio chip bases which
are also used for the offset-calculations. Now both setting and resetting
the chip selects works as expected from userland and from the kernelspace.
Signed-off-by: NPeter Turczak <peter@turczak.de>
Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      89127ed3
    • G
      m68k: fix memcpy to unmatched/unaligned source and dest on 68000 · f230e80b
      由 Greg Ungerer 提交于 
      The original 68000 processors cannot copy 16bit or larger quantities from
odd addresses. All newer members of the 68k family (including ColdFire)
can do this.

In the current memcpy implementation after trying to align the destination
address to a 16bit boundary if we end up with an odd source address we go
off and try to copy multi-byte quantities from it. This will trap on the
68000.

The only solution if we end with an odd source address is to byte wise
copy the whole memcpy region. We only need to do this if we are supporting
original 68000 processors.
Signed-off-by: NGreg Ungerer <gerg@uclinux.org>
      f230e80b
  11. 28 9月, 2011 1 次提交
    • P
      doc: fix broken references · 395cf969
      由 Paul Bolle 提交于 
      There are numerous broken references to Documentation files (in other
Documentation files, in comments, etc.). These broken references are
caused by typo's in the references, and by renames or removals of the
Documentation files. Some broken references are simply odd.

Fix these broken references, sometimes by dropping the irrelevant text
they were part of.
Signed-off-by: NPaul Bolle <pebolle@tiscali.nl>
Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      395cf969
  13. 12 9月, 2011 1 次提交
  15. 27 8月, 2011 1 次提交
  17. 24 8月, 2011 1 次提交
  19. 03 8月, 2011 1 次提交
  21. 31 7月, 2011 4 次提交