From: Meelis Roos <mroos@xxxxxxxx> Date: Wed, 8 Jun 2011 15:40:33 +0300 (EEST) > I see this on 500 MHz Fire V100. > > [ 59.253164] calibrate_delay_direct() timer_rate_max=55726 timer_rate_min=55504 pre_start=329128453 pre_end=329184069 > [ 59.283196] calibrate_delay_direct() timer_rate_max=55721 timer_rate_min=55503 pre_start=329295308 pre_end=329350920 > [ 59.313228] calibrate_delay_direct() timer_rate_max=55722 timer_rate_min=55502 pre_start=329462156 pre_end=329517768 > [ 59.343261] calibrate_delay_direct() timer_rate_max=55723 timer_rate_min=55505 pre_start=329629002 pre_end=329684616 > [ 59.373293] calibrate_delay_direct() timer_rate_max=55718 timer_rate_min=55499 pre_start=329795855 pre_end=329851464 > [ 59.373349] Calibrating delay using timer specific routine.. 11.14 BogoMIPS (lpj=55722) > > 11 bogomips seems ... slow. Older machines like Ultra 1, Ultra 5/10 show > double the CPU clock speed as bogomips. Is it normal or is something > clock-related broken? It has to do with what clock source we're using for timer interrupt generation, and for this CPU we use the system TICK value which runs at the bus clock speed and not the CPU clock speed. Absolutely no interpretation of the bogomips value should ever be made. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
