[PATCH 02/12] score: Add ticks per second to configuration

[Chris Johns]

On 8/04/2016 5:35 PM, Sebastian Huber wrote:
> On 08/04/16 09:06, Chris Johns wrote:
>> I assume the microsecond, nanosecond and tick per sec values all need
>> to agree.
>>
>> Does anything check this is the case and raise a fatal error if they
>> do not?
>
> Currently nobody checks this. Should we check this via an _Assert()? If
> we add new fatal errors, it will get difficult. We need to test it.

Yes an assert is perfect. It is a hard config error.

> The
> Configuration is read-only. We would have to avoid <rtems/confdefs.h> to
> create a corrupt Configuration and this is very bad.

It is not recommended anyone manually create their own Configuration 
table but there is nothing that says you _have_ to use confdefs.h. I do 
remember the pre-confdefs days.

If we create a dependence we should ensure things are within spec before 
continuing.

Chris