[U-Boot] [RFC] Review of U-Boot timer API

Wolfgang Denk wd at denx.de
Wed May 25 22:48:58 CEST 2011


Dear "J. William Campbell",

In message <4DDD6930.2080202 at comcast.net> you wrote:
>
> methods are functionally identical. The only problems arise on systems 
> that don't support interrupts and don't have any timers with enough bits 
> available to meet the 4294967 seconds maximum interval requirement. 

Where exactly is this requirement coming from?

>      Right now, almost all ARM cases are broken, because they have short 
> timers and don't use interrupts. In some cases, there are actual bugs 
> involved. We can make these cases less broken than they now are with a 
> common get_timer approach as outlined previously. However, we cannot fix 

We could also make them use interrupts for this type of timer service?

How do these systems implement system time in other environments, say
in Linux?  Or in Barebox?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Human beings were created by water to transport it uphill.


More information about the U-Boot mailing list