SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Politics : Formerly About Advanced Micro Devices -- Ignore unavailable to you. Want to Upgrade?


To: Elmer who wrote (59121)5/21/1999 4:56:00 PM
From: Kevin K. Spurway  Read Replies (2) | Respond to of 1572264
 
Re:"I get my first non-AMD K7 motherboard within the next month, along with an updated revision of the K7"

Typical that you would try to construe this as news that the K7 hasn't been debugged yet. IMHO, the interesting part of that comment to me is the non-AMD chipset availability. Very reassuring.

Kevin



To: Elmer who wrote (59121)5/21/1999 6:09:00 PM
From: RDM  Respond to of 1572264
 
Re: "First Elmer makes a baseless statement: If Anand is right there still isn't a fully debugged K7."

Anand is not saying anything like that! He simply says that he is not priviledged to new revision machine. Anand's machine was likely built in February or March. This was a time when some on this thread thought that the K7 was not working nearly at this level.

It is clear, IMHO, that the machine that Anand has is working at a gross level boots and executes code. However, it it still has bugs. From my experience a whole lot of debugging can go on in three months. Maybe four or five generations of revised chips have been built since his machine.

I doubt AMD will give him a newer machine until closer to the launch. Even if they announce the chip next week, they may not give
him a machine for a week or two after that. After all the first official benchmarks will be released at 8:30 PM June 10 in Santa Clara.

The historic source of bugs are not the risk, AMD has extensive testing software so that the Intel Fdiv bug will not likely happen. There is unfortunately the unknown.