------- io-api.txt -------
404,405c404,421
< 	If an error occurs during the read, set ret1 (error_flag) to
< 	a non-zero value.
---
> 	If an error occurs during the read, ret1 (error_flag) shall be set
> 	to one of the following values:
> 
> 	0x1 indicates that the config space register access did not succeed
> 	due to an unspecified error. This error_flag value is deprecated
> 	and is only used by older implementations of this API that did not
> 	distinguish between CRS and non-CRS errors.
> 
> 	0x2 indicates that the config space register access did not succeed
> 	due to an error other than Config Request Retry Status(CRS).
> 
> 	0x4 indicates that the config space register access did not succeed
> 	due to CRS.
> 
> 	Note: Earlier implementations of this API returned the value 0x1
> 	in ret1 for all errors. The API only specified that a non-zero value
> 	in ret1 indicated an error. There was no way to distinguish between
> 	CRS or any other error.
440,442c456,473
< 	If an error occurs during the write access, do not generate
< 	an error report, do set ret1 (error_flag) to a non-zero value.
< 	Otherwise, set ret1 to zero.
---
> 	If an error occurs during the read, ret1 (error_flag) shall be set
> 	to one of the following values:
> 
> 	0x1 indicates that the config space register access did not succeed
> 	due to an unspecified error. This error_flag value is deprecated
> 	and is only used by older implementations of this API that did not
> 	distinguish between CRS and non-CRS errors.
> 
> 	0x2 indicates that the config space register access did not succeed
> 	due to an error other than Config Request Retry Status(CRS).
> 
> 	0x4 indicates that the config space register access did not succeed
> 	due to CRS.
> 
> 	Note: Earlier implementations of this API returned the value 0x1
> 	in ret1 for all errors. The API only specified that a non-zero value
> 	in ret1 indicated an error. There was no way to distinguish between
> 	CRS or any other error.