Searched hist:"04 b75b10" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/m68k/include/asm/ |
| H A D | m5272sim.h | 04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
|
| H A D | m5206sim.h | 04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
|
| H A D | m5407sim.h | 04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
|
| H A D | m5307sim.h | 04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
04b75b10 Mon May 18 23:52:40 CDT 2009 Greg Ungerer <gerg@uclinux.org> m68knommu: simplify ColdFire "timers" clock initialization
The ColdFire "timers" clock setup can be simplified. There is really no
need for the flexible per-platform setup code. The clock interrupt can be
hard defined per CPU platform (in CPU include files). This makes the
actual timer code simpler.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
|