Alan> x86_udelay_tsc wont have been set at that point so the main
Alan> timer is still being used.
>> x86 does use current_cpu_data.loops_per_jiffy in the non-TSC
>> case, no?
Alan> I believe so. So we should propogate that across earlier,
Alan> although its not needed for our current console drivers that I
Alan> can see
I don't think you can do it early enough. calibrate_delay() requires
irqs to be enabled and the first printk() happens long before irqs are
enabled on an AP.
--david
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/