I have been designing silicon chips for longer than I wish to admit. Making metal revision to a mask set is a very standard process. Usually the errors are detected in testing in the lab. Thinking that you have a final product and later finding from a customer that it still contains a bug happens frequently too. You would expect it happens less at large company as Intel due to an army of design verifiers they have nevertheless this clearly happens from time to time (there was a big Intel recall few years back). The truth is that a sheer complexity of microprocessor or number of permutations required in testing is so large that you actually never know for sure that silicon is working all the time!...dr Kris
I fully agree with DrizztVD. What kind of world are we living in? Mistakes are only human and all of us make mistakes whether we admit it or not. And if a company fires its employees for making a mistake, its only creating fear and in future nobody will be eager to do new things.
Its not unfortunate to have errors, its unfortunate not to admit it.
You'd have to be a very messed up manager to want to fire your engineers for something they had no control over. This is not a case of negligence, it is a case of straightforward trail-and-error learning. And it's not embarrassing either, these things happen all the time. Kudos to Intel for doing the right thing and withholding chips until they have reliable chips to sell. Lesser companies would have tried to cover it up.
Intel admitting that it is a "design oversight" is really unfortunate. This is the risk involved in having a basic design issue as it seeps into other blocks making its impact catastrophic. Surely many heads would have rolled down in the aftermath of this. But certainly it is " Better Late than Never".
Blog Doing Math in FPGAs Tom Burke 16 comments For a recent project, I explored doing "real" (that is, non-integer) math on a Spartan 3 FPGA. FPGAs, by their nature, do integer math. That is, there's no floating-point ...