diff options
author | 2011-10-19 13:24:24 +1000 | |
---|---|---|
committer | 2011-12-30 10:20:43 +1000 | |
commit | 4a13c6dc6443786b135c9e9b3f9dc87421cc1ae3 (patch) | |
tree | 46b74b6ac63dcce31a2a34e8f49541cb3b857895 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | m68k: add code to setup a ColdFire 54xx platform when MMU enabled (diff) | |
download | wireguard-linux-4a13c6dc6443786b135c9e9b3f9dc87421cc1ae3.tar.xz wireguard-linux-4a13c6dc6443786b135c9e9b3f9dc87421cc1ae3.zip |
m68k: ColdFire with MMU enabled uses same clocking code as non-MMU
We want to use the same timer support code for ColdFire CPU's when
running with MMU enabled or not. So use the same time_no.c code even
when the MMU is enabled for ColdFire. This also means we do not want
CONFIG_ARCH_USES_GETTIMEOFFSET set, since that code is only in time_mm.c.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Acked-by: Matt Waddel <mwaddel@yahoo.com>
Acked-by: Kurt Mahan <kmahan@xmission.com>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions