With Hammer, there are no accessible bridges. With Hammer and its Hypertransport, everything is is point to point/switched. There is no system bus to overclock. There is no "FSB" to increase from 133 to 166, or 166 to 200.
For those that don't recall, the memory controller is integrated on the Hammer processor die, and it eliminates the traditional system bus; this feature should substantially reduce memory latency. The integrated memory controller on Clawhammer is 64-bit (single channel DDR), and will run at 133MHz or 166MHz, but again, there is no system bus to change or configure through the bios. There is no way to change memory timings, since these are predefined in the processor's core logic.
If it is impossible to overclock Hammer...how will that impact its adoption in the enthusiast scene?
For those that don't recall, the memory controller is integrated on the Hammer processor die, and it eliminates the traditional system bus; this feature should substantially reduce memory latency. The integrated memory controller on Clawhammer is 64-bit (single channel DDR), and will run at 133MHz or 166MHz, but again, there is no system bus to change or configure through the bios. There is no way to change memory timings, since these are predefined in the processor's core logic.
If it is impossible to overclock Hammer...how will that impact its adoption in the enthusiast scene?