Re: [U-Boot] [RFC PATCH] lib/timer: initialize timebase_l/timebase_h

2016-11-04 Thread Andre Przywara
Hi, On 26/10/16 08:14, Alexander Graf wrote: > On 10/26/2016 02:07 AM, André Przywara wrote: >> On 25/10/16 08:52, Alexander Graf wrote: >> >> Hi Alex, >> >> thanks for looking at this! >> >>> On 25/10/2016 02:51, Andre Przywara wrote: On systems using the generic timer routines defined in

Re: [U-Boot] [RFC PATCH] lib/timer: initialize timebase_l/timebase_h

2016-10-26 Thread Alexander Graf
On 10/26/2016 02:07 AM, André Przywara wrote: On 25/10/16 08:52, Alexander Graf wrote: Hi Alex, thanks for looking at this! On 25/10/2016 02:51, Andre Przywara wrote: On systems using the generic timer routines defined in lib/time.c we use timebase_l and timebase_h fields from the gd to

Re: [U-Boot] [RFC PATCH] lib/timer: initialize timebase_l/timebase_h

2016-10-25 Thread André Przywara
On 25/10/16 08:52, Alexander Graf wrote: Hi Alex, thanks for looking at this! > > On 25/10/2016 02:51, Andre Przywara wrote: >> On systems using the generic timer routines defined in lib/time.c we >> use timebase_l and timebase_h fields from the gd to detect wraparounds >> in our tick counter.

Re: [U-Boot] [RFC PATCH] lib/timer: initialize timebase_l/timebase_h

2016-10-25 Thread Alexander Graf
On 25/10/2016 02:51, Andre Przywara wrote: > On systems using the generic timer routines defined in lib/time.c we > use timebase_l and timebase_h fields from the gd to detect wraparounds > in our tick counter. The tick calculcation algorithm silently assumes > that a long is only 32 bits, which

[U-Boot] [RFC PATCH] lib/timer: initialize timebase_l/timebase_h

2016-10-24 Thread Andre Przywara
On systems using the generic timer routines defined in lib/time.c we use timebase_l and timebase_h fields from the gd to detect wraparounds in our tick counter. The tick calculcation algorithm silently assumes that a long is only 32 bits, which leads to wrong results when timebase_h is not 0 on