> > Well, loop_delay() was big (fatal!) problem -- it can actaully wait
> > for *less* time than told to. That happens if notebook boots during
> > "battery low" and than goes to AC power. Thinkpad 560X is example of
> > such behaviour. Slow (but working!) PIT seems to be only option on
> > such machine.
>
> I need to look more at the cpu_freq code, but I suspect it could it help
> solve or lessen the problem (if we can detect the event on those
> > older
> systems). Regardless, you make a good point, so if I get the time
> > I'll
It is possible to lessen the problem by measuring speed and
recalibrating if it changes, but due to delay between measuring and
recalibrating it is still not 100% reliable.
> look into a real PIT based delay.
>
-- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. - 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/