Dg B wrote:
> problem. If the CPU was not designed to handle this kind of speed, then
> Intel should really go down to the floor of their manufacturing plants,
> because they are building chips that are definitely outstripping the
> "...operating limits..." as stated by the design engineers. Then again,
> maybe it is not the designers who are making these decisions...
The 300MHz components were taken straight out of the 450MHz P-II production
line, so maybe they WERE designed for this.
On the other hand, Intel knows a lot more about the devices than you
and I.
If they have a batch that does not tolerate 2.2V Core, and with 2.0V
Core it may only achieve 400MHz. But with tolerances on input voltage
and allowed case temp, it may only achieve 325MHz. So if you "quickly"
test it it may seem to work just fine at 2.2V and 450MHz, but in fact
you're wearing your chip down a lot faster than intended, and you're
likely to hit a limit under some "extreme" circumstances at some time
in teh future.
But then again, 450 MHz may just work fine for all eternity.
While debugging the hang problem, I find it best to try to remove the
"overclocking" variable from the process...
Roger.
--
** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
"I didn't say it was your fault. I said I was going to blame it on you."
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
