> > > > -#define COUNT_TO_USEC(x) ((x) * 16 / 133)
> > > > +#define COUNT_TO_USEC(x) ((x) / 133 * 16)
> > >
> > > Before the change, the result is useful for all values of x in the
> > > interval from 0 through UINT_MAX/16 = 268435455 = 268 seconds, i. e.
> > > for all values that make
Dear Lee Jones,
In message <20121121100228.gj28...@gmail.com> you wrote:
>
> > > -#define COUNT_TO_USEC(x) ((x) * 16 / 133)
> > > +#define COUNT_TO_USEC(x) ((x) / 133 * 16)
> >
> > Before the change, the result is useful for all values of x in the
> > interval from 0 through UINT_MAX/16 = 2684354
> > If we attempt to take a 32bit timer value and multiply it by a
> > significant number, the core will not be able to handle it. This
> > gives the illusion that the timer is rolling over, when in fact
> > this is not the case. If we ensure the division in this instance
> > is carried out before
Dear Lee Jones,
In message <1353422034-28107-2-git-send-email-lee.jo...@linaro.org> you wrote:
> If we attempt to take a 32bit timer value and multiply it by a
> significant number, the core will not be able to handle it. This
> gives the illusion that the timer is rolling over, when in fact
> thi
If we attempt to take a 32bit timer value and multiply it by a
significant number, the core will not be able to handle it. This
gives the illusion that the timer is rolling over, when in fact
this is not the case. If we ensure the division in this instance
is carried out before the multiplication,
5 matches
Mail list logo
