RegisterElements cross-company collation first-pass

Folks;

I've made a first pass attempt to put the three 
register element lists submitted to the twiki thus far into a single 
spreadsheet. I'm thinking this will allow us to more easily do a side-by-side 
comparison of what each member company requires in the data 
model.

Two things jump out at me:

  

  
The list from IBM is more comprehensive of what 
  customers expect to see in the memory map / register documentation, 
  but doesn't include the structural relationships of the 
  elements.

  

  
The lists from PDTi and Freescale are very sparse, 
  but clearly show the element relationships.

So we've obviously got to find a merging of these two 
approaches in order to facilitate both goals of this team: to support 
information interchange (commonly used elements in a consistent data structure) 
and meet the needs of our customers more easily (comprehensive 
human-readable information sets).

 

One other thing I notice ... we might look at 
collecting the elements into categories to help in the process of 
cross-collating the way each of us has identified things in the 
past:

  
physical location (addresses, offsets, ranges, 
  etc.)

  
names (register and field 
  mnemonics)

  
descriptions (short, long, state-related, 
  etc.)

  
attributes (access types, reset values, 
  etc.)

Looking forward to a lively discussion 
today...

Respectfully,
Bob 
Beims

Applications Engineer, Staff 
Principal
Transportation & Standard Products Group, Microcontroller 
Division

  
  

    
      
Freescale 
      Semiconductor, Inc.
6501 William Cannon Drive West, MD: 
      OE49    
Austin, TX 
      78735-8598
www.freescale.com
 

    T:
F:

    512 895 6956
512 
      895 3585

This e-mail, and any 
associated attachments have been classified as:
[X]Public
[ ]Freescale Semiconductor Internal 
Use Only
[ ]Freescale Semiconductor Confidential 
Proprietary

RegisterElements_collation.xls