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: Windsock who wrote (77376)10/27/1999 3:58:00 PM
From: Michael DaKota  Respond to of 1577319
 
"Please explain why the Intel hardware works and the AMD hardware does not work if it is a software problem"

you are missing the point here.
It's not "AMD hardware" but "K6-x" cpu's not working.
The reason is that the before mentioned critical timing on op codes in the usb driver is screwing up.
Intel cpu's have something in the order of 4x longer latency on a certain instruction (Really, dont bite me here, im terrible on the inner workings of cpu's ;)than the k6 line, thus causing the timing errors.
AMD fixed this by also implementing that very long and slow latency on that particular instruction in their k7 series , albeit not because it improved the overall design, but for compatibilities sake.

If anyone has a more advanced and detailed explenation (with the "instruction" named properly etc;) , please do, I forgot the exact nature of the problem ages ago.



To: Windsock who wrote (77376)10/27/1999 9:48:00 PM
From: Steve Porter  Respond to of 1577319
 
Windsock,

The problem exists because microsoft wrote timing loops based on teh execution speed of a couple of x86 instructions. On Intel processors these insturctions takes 2 clocks, and on k6 processors tehy take 1 clock. Therefore they BREAK on the AMD processors, because the AMD processor executes them too quicly..

Steve