OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-sidsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dita-sidsc] bitFieldReset issue


Ah. So I should be using "value" and "trigger", as in:
 
<bitFieldReset> 
   <bitFieldResetValue>1</bitFieldResetValue> 
   <bitFieldResetTrig>POR</bitFieldResetTrig>
</bitFieldReset>
 
Cool. I just got hung up on the word "source".
 
Thx.
 
-sp
 
--------------------------------------------
seth park
information architect
Freescale Semiconductor, Inc.
seth.park@freescale.com
512.895.2463
 


From: Austin Mike-B07417
Sent: Monday, January 11, 2010 11:35 AM
To: Park Seth-R01164; Semiconductor Information Design Subcommittee
Subject: RE: [dita-sidsc] bitFieldReset issue

Actually, I think there's a slight disconnect here.
 
Isn't the bitFieldresetValueSource specifying a signal, which has it's own value? It's not saying what causes the reset, just that the value on reset is going to be whatever the value of that signal is.
 
I'm not sure that solves your problem but I don't think ...ValueSource can be used the way you want to use it.
 
Mike Austin
MSG IMM Information Architect
Freescale Semiconductor, Inc.
512-895-8910    mike.austin@freescale.com


From: Park Seth-R01164
Sent: Monday, January 11, 2010 11:11 AM
To: Semiconductor Information Design Subcommittee
Subject: [dita-sidsc] bitFieldReset issue
Importance: High

I'm having trouble understanding the intent of the bitFieldRest rules in the most recent lang spec (http://www.oasis-open.org/apps/org/workgroup/dita-sidsc/download.php/32513/ditaref-sidsc-book-d-090512-review.pdf)
 
It says that "The <bitFieldResetValue> and <bitFieldresetValueSource> elements are mutually exclusive," which means that you can have...
 
EITHER
 
<bitFieldReset> 
   <bitFieldResetValueSource>HRESET</bitFieldResetValueSource> 
   <bitFieldResetTrig>System Reset</bitFieldResetTrig>
</bitFieldReset>
 
OR
 
<bitFieldReset> 
   <bitFieldResetValue>0</bitFieldResetValue> 
   <bitFieldResetTrig>System Reset</bitFieldResetTrig>
</bitFieldReset>

BUT NEVER
 
<bitFieldReset> 
   <bitFieldResetValue>0</bitFieldResetValue> 
   <bitFieldResetValueSource>System Reset</bitFieldResetValueSource>
</bitFieldReset>

 
I'm trying to capture a field definition of a field that has a different reset value when the reset source is from a "Power on Reset". When it is a system reset, the field resets to "0"; when it is a POR, it resets to "1". But the data model does not allow this combination.
 
Can we agree that this is a valid combination and that the DTD/spec should be relaxed?
 
 
-seth
--------------------------------------------
seth park
information architect
Freescale Semiconductor, Inc.
seth.park@freescale.com
512.895.2463
 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]