Prev: nfs kernel server causes: kernel BUG at include/linux/module.h:386!
Next: [PATCH] USB: tty: fix incorrect use of tty_insert_flip_string_fixed_flag
From: Jacob Pan on 7 May 2010 13:50 Hi hpa, ingo, and tglx, The following changes are based on commit: d94e93d495514c69d4a7a553c0938cd777267e5d Changes include addition of vitual RTC driver and many clockevent tweaks in order to support Medfield (next generation) in the same binary kernel image. We consolidated tsc and lapic calibration into platform specific routine under x86_init for MRST. There will be a follow-up RFC patch does the similar consolidation for standard PC with HPET. *** BLURB HERE *** Feng Tang (2): x86/platform: add a wallclock_init func to x86_platforms ops x86/mrst: add vrtc driver which serves as a wall clock device Jacob Pan (6): x86: avoid check hlt if no timer interrupts x86/mrst/pci: return 0 for non-present pci bars x86/apic: allow use of lapic timer early calibration result x86/mrst: change clock selection logic to support medfield x86/apbt: support more timer configurations on mrst x86/mrst: Add nop functions to x86_init mpparse functions arch/x86/include/asm/apb_timer.h | 2 +- arch/x86/include/asm/bugs.h | 1 + arch/x86/include/asm/fixmap.h | 4 + arch/x86/include/asm/mrst.h | 30 ++++++++ arch/x86/include/asm/vrtc.h | 27 +++++++ arch/x86/include/asm/x86_init.h | 2 + arch/x86/kernel/Makefile | 2 +- arch/x86/kernel/apb_timer.c | 18 +++-- arch/x86/kernel/apic/apic.c | 21 +++++- arch/x86/kernel/cpu/bugs.c | 4 + arch/x86/kernel/mrst.c | 143 ++++++++++++++++++++++++++++++++++--- arch/x86/kernel/setup.c | 2 + arch/x86/kernel/vrtc.c | 100 ++++++++++++++++++++++++++ arch/x86/kernel/x86_init.c | 2 + arch/x86/pci/mrst.c | 2 +- 15 files changed, 336 insertions(+), 24 deletions(-) create mode 100644 arch/x86/include/asm/vrtc.h create mode 100644 arch/x86/kernel/vrtc.c -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |