[U-Boot] [RFC][Timer API] Revised Specification - Implementation details

Wolfgang Denk
2011-05-27T07:48:32Z

Dear Graeme Russ,

In message <4DDF543D.6020506@gmail.com> you wrote:
>
> >> I think we will need to define get_timer() weak - Nios will have to
> >> override the default implementation to cater for it's (Nios') limitations
> >
> > Please don't - isn't the purpose of this whole discussion to use
> > common code for this ?
> >
>
> Yes, but Nios is particularly bad - It has a 10ms tick counter :(
>
> I don't see reason for hamstring other platforms when a simply weak
> function can get around it

Why does NIOS require a different get_timer() implementation?

Nobody claims that get_timer() has any specific resolution. It is
perfectly legal that a loop like

for (;;) {
u32 t = get_time();

printf("t=%ul\n", t);
}

returns 100 millisecond increments.

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
A girl with a future avoids the man with a past.
-- Evan Esar, "The Humor of Humor"