Next: HDMC Module Parts (1)
Up: l1joint_0330_hdmc
Previous: HDMC Bitfield Access (2)
Problems and Unresolved Issues
- Register format is defined in configuration file, but readonly
flags are in the parts file. Should/could they be moved?
[NB these flags may change to support verify() method].
- Create one class per register format? Or one class per register
part per module?
- Ideally, only define read functions for readable bits and write
functions for writeable bits.
- Check that value for sparse ``bit menu'' type field is one of
the known values; exception if not?
- Check that value for bit field is within range of bit field
size; exception if not?
- Should Register (or suitable subclass) cache the last value
read or written. Otherwise write functions need read/modify/write
cycle.
- Should bit field manipulation functions actually write back the
new register value; or use a separate MyReg::write() using the
modified cached value? Or provide both options?!
- With a compiler, these choices are simple to change...
Next: HDMC Module Parts (1)
Up: l1joint_0330_hdmc
Previous: HDMC Bitfield Access (2)
Murrough Landon (m.p.j.landon@qmw.ac.uk)