Quote:
Originally Posted by Shauk
well I'm wondering just how simple of a fix it is. They're either using a different revision of the syscon chip in the slims that don't have that firmware bug or it's just a more current version.
still I think even if you knew anything about programming, it seems like one of those things you'd want to carefully program since firmware is a one shot pony. If it messed up, you brick the ps3. permadeath is a lot more serious than a 24 hour "oops"
So they'd have to write the code to identify the chip on each unique revision of the ps3, even the slim, code the slim to NOT run the code and still tell the slim that the patch was successful, lol.
I dunno deploying an update to 40 million ps3 owners is a risk, it takes a lot of QA. I'm sure they're aware of it now but it's not something I would have expected them to pop out in 24 hours.
The whole apocolyPS3 thing could have been a lot lot worse than it really was, haha.
|
Assuming they did use a different revision of the syscon chip then it should have an identifier. All the firmware programmers would have to do is add some kind of check into the code (if version=1.0 then upgrade) Assuming 1.0 is the id of the older syscon chip. Granted that's vastly simplified but it shouldn't be all that difficult.
Quote:
Originally Posted by YaWhateva
If this is Sony's biggest bug with the PS3 then I'm happy. At least it's not an RROD.
|
It's funny that you mention RROD. I've actually been debating about tearing into my 60GB to replace the thermal grease with something of a better quality, but I haven't worked up the nerve yet.
__________________
"I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all other possible gods, you will understand why I dismiss yours." -Stephen F. Roberts
IF PWNED > OWNED and PWNED=PWNAGE and OWN<PWN but PWN<PWNED and OWNAGE>OWN then what does OWNAGE+PWN equal?