Fw: SIDSC Spec Review Issue to Resolve

[Annette Bauerle <abauerle@us.ibm.com>]

Regards,

Annette

Annette Bauerle, PMP
Team Lead, PowerPC Information Development
Systems & Technology Group
802-769-4223 • (T/L 446-4223) • Fax: 8-446-7147
IBM, Essex Junction, VT 05452
----- Forwarded by Annette
Bauerle/Burlington/IBM on 05/13/2009 11:53 AM -----

Annette Bauerle/Burlington/IBM

05/12/2009 05:54 PM

To	Noreen.McMahan@freescale.com
cc
Subject	Re: SIDSC Spec Review Issue to ResolveLink

Hi Noreen.

Thanks for reviewing and researching
all the comments. 

For good or ill, we seem to have three
types  of reserved bits.  Not all types are present in all products.


Reserved:        
Bits are not implemented; all bits read back zero    
               
    (equivalent to URZ)
Rsvd_I:        
Latch bits are implemented; value read is the value written.  
     (a new type of reserved bit)
Reserved:        Reserved
fields are written as 0 and read as undefined        
        (equivalent to R?)

Regards,

Annette

Annette Bauerle, PMP
Team Lead, PowerPC Information Development
Systems & Technology Group
802-769-4223 • (T/L 446-4223) • Fax: 8-446-7147
IBM, Essex Junction, VT 05452

Noreen.McMahan@freescale.com

05/12/2009 10:31 AM

To	Annette Bauerle/Burlington/IBM@IBMUS
cc
Subject	SIDSC Spec Review Issue to Resolve

Hello Annette, you raised a number of important issues
in your spec review, some of which will be open for further group discussion.
Following is one we'd like you to prepare for discussion. Thanks!

p. 84. bitFieldAccess. Annette asks: Are we restricted to the values defined
here? (Does DITA check?) I think there's at least one more possibility
for a reserved field (I'll have to verify.) 
Bob: We are not restricted and DITA is not going to check. This would have
to be tool enforcement. Annette, please check and let us know about whether
you have another case for reserved. 

--Noreen

S/MIME Cryptographic Signature