> /* > * CLOCK_TICK_RATE is traditionally the base frequency using the PC-style > * i8253 "PIT" timer. Architecture independent device drivers should not > * rely on this value. > * Any architecture that either has a real PC-style PIT, or does not have a > * fixed timer interval at all and just needs to provide some value here > * should just fall back to this default. > */ They shouldn't define it - we want those invalid cases to error. Stick CLOCK_TICK_RATE in the depths of the x86 arch includes and then we can fix the other cases properly. Either the device has an independant clock of the same frequency (some watchdogs do this), it relies upon a motherboard timer in which case the platform can define CLOCK_TICK_RATE (or a better name for it), or it doesn't have any meaning in which case we *want* it not to compile. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
