Greg Ungerer wrote:
> >>Looking at this isn't it mis-handling the case where the
> >>TCN reads back as the maximal count (so ticks_per_intr in
> >>this case).
> >
> >Well thought :)
> >
> >>My understanding is that could occur after it
> >>has clocked over to the maximal count value, and after we
Hi Philippe,
Philippe De Muyter wrote:
Greg Ungerer wrote:
Philippe De Muyter wrote:
The coldfire timer runs from 0 to trr included, then 0 again and so on.
It counts thus actually trr + 1 steps for 1 tick, not trr. Fix that
Actual debugging work has been made on a 5272. I hope it's the same
Hi Greg,
Greg Ungerer wrote:
> Hi Philippe,
>
> Philippe De Muyter wrote:
> >The coldfire timer runs from 0 to trr included, then 0 again and so on.
> >It counts thus actually trr + 1 steps for 1 tick, not trr. Fix that
> >Actual debugging work has been made on a 5272. I hope it's the same for
Hi Philippe,
Philippe De Muyter wrote:
The coldfire timer runs from 0 to trr included, then 0 again and so on.
It counts thus actually trr + 1 steps for 1 tick, not trr. Fix that
Actual debugging work has been made on a 5272. I hope it's the same for
the other coldfire's.
Signed-off-by: Phili
The coldfire timer runs from 0 to trr included, then 0 again and so on.
It counts thus actually trr + 1 steps for 1 tick, not trr. Fix that
Actual debugging work has been made on a 5272. I hope it's the same for
the other coldfire's.
Signed-off-by: Philippe De Muyter <[EMAIL PROTECTED]>
diff -r
