> Well, to me READ_TIMER() sounds like a function/macro to read some > value from some timer; if that timer counts doen, then successive > calls to that macro/function would return decreasing values. Counting > up or down is a property of the specific timer and should be handled > elsewhere; such policy does IMHO not belong into some accessor > function.
Well, I thought this was an easy fix. Unfortunately, I can't test any new code for a few days, so a patch that changes this, while trivial, may be bugged. Unless I get an ack from you, I'll send a timer which negates elsewhere in a day or so. /alessandro _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
