Re: RST# Timing ECN

[Chris Myers <myers@gateway.quatech.com>]

** Reply to note from "Scott Eichman" <seichman@simpact.com> Thu, 26 Feb 1998   
09:35:09 -0800 
 
> We have seen the "problem" of fast system configuration reads. The AMCC 
> device is ready to respond to the reads, and does so. It just does it before 
> the serial ROMs "soft" configuration is completed. The result is that the 
> AMCC defaults are in the system configuration tables and our driver can't 
> find "us" because it is looking for our VID and DID values.  
 
	The AMCC 5933 data book states in section 7.1 that the chip will retry   
until it either determines that no boot prom exists or the configuration   
download from the boot prom is complete.  I don't see the problem you mention   
on the latest errata sheet I have.  We haven't used the 5933 --- yet, but I   
haven't seen this problem with the 5920. 
	The way I read AMCC's databook, if you have found this kind of   
behavior, it is their bug to fix. 
 
	I will add that I agree with you on the use of "must" rather than   
"should" for the delay after RST#. 


Best regards,

Chris Myers
Electronic Project Engineer
Quatech, Inc.
myers@quatech.com