Searched hist:"4 a13c6dc6443786b135c9e9b3f9dc87421cc1ae3" (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/arch/m68k/kernel/ |
H A D | time.c | diff 4a13c6dc6443786b135c9e9b3f9dc87421cc1ae3 Tue Oct 18 22:24:24 CDT 2011 Greg Ungerer <gerg@uclinux.org> 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>
|
/openbmc/linux/arch/m68k/ |
H A D | Kconfig | diff 4a13c6dc6443786b135c9e9b3f9dc87421cc1ae3 Tue Oct 18 22:24:24 CDT 2011 Greg Ungerer <gerg@uclinux.org> 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>
|