randycat99
Veteran
Is this an inopportune moment for a joke referring to an upcoming announcement to reveal that the lower speed will be the "core" version and the higher speed will be the "deluxe" version?
xbdestroya said:***UPDATE***
Well, Fouad - I guess you were right. Indeed in Microsoft's NDA'd developer notes, they indicate the final tri-core design at 3 GHz rather than 3.2 GHz. Now I'm not sure what the significance of this is; honestly I still think 3.2 would be what to expect. But indeed you are vindicated in having preached what you were preaching.
Taken from the document: 'Xbox 360 Alpha vs. Final Hardware Performance'
Keep in mind within the doc itself it states that specs could change substantially prior to release, and that the doc itself is an early release. So again I'm still going with the 3.2 GHZ Microsoft stated, but indeed the doc we were both quoting *does* say 3 GHz.
Going back to a question I asked earlier in this discussion, does anyone know the FSB frequency for the XeCPU chipset/CPU? I'm wondering what the clock multiplier would even have to be to run at 3 GHz. For some reason I had been thinking 400 MHz clock multiplier increments before.
Panajev2001a said:I wonder who has not glanced over those docs... We are making a big fuss over nothing: expect 3.2 GHz chips in the retail machines (there are developers with 3.2 GHz XeCPU's so, there goes the theory ).
Probably one or a couple surface-mount resistors being soldered into the wrong place, setting an incorrect multiplier. That's my guess. It doesn't seem as if the chips themselves are different, and I wouldn't expect them to be either.Jawed said:Because the CPU is locked at 2.8GHz at the time of kit assembly there is no software fix to tweak the frequency to 3.2GHz
Guden Oden said:Probably one or a couple surface-mount resistors being soldered into the wrong place, setting an incorrect multiplier. That's my guess. It doesn't seem as if the chips themselves are different, and I wouldn't expect them to be either.
Jawed said:I can't believe some people still think this is anything other than a manufacturing mistake.
Devs already have 3.2GHz debug and dev kits. It's just that some of them got made wrong. A juicy bit of gossip that I couldn't let pass...
Jawed
The clockspeed is determined after the chip's been manufactured, during chip functionality verification. It would make no sense to fabricate lower clocked chips to test with, because they'd be completely different compared to the real chips; essentially a different product... Besides, the manufacturing process used for these chips is NOT new. In fact it's quite mature by now.Powderkeg said:Or someone could have grabbed a batch of pre-production sample CPU's on accident, which seems much more likely. After all, they would have done a run of lower-clock speed CPU's to test the fabrication process before they started mass producing the final CPU's.
I don't see how that would have been the case. These things aren't soldered together by hand. They're built in automated plants.It's quite possible that they could have had a box of those pre-production samples lying around in the same area as the first final-spec chips were produced, and they may have been mixed in on accident.
SDKs typically cost LOTS (50-ish K US$, maybe more I suppose), but then you also have to pass qualifications to even be allowed to buy one. I highly doubt just any guy could order a devkit, even if he/she has the money to blow on one.DarkRage said:How much do they cost?
Guden Oden said:The clockspeed is determined after the chip's been manufactured, during chip functionality verification. It would make no sense to fabricate lower clocked chips to test with, because they'd be completely different compared to the real chips; essentially a different product... Besides, the manufacturing process used for these chips is NOT new. In fact it's quite mature by now.
I don't see how that would have been the case. These things aren't soldered together by hand. They're built in automated plants.
Like I said, I very VERY much doubt the lower-clocked and fully-clocked machines use CPUs that are different, they probably just have different multipliers set, either on the CPU substrate or on the motherboard.