Hi,

Arjan van de Ven wrote:
quoted text
> On 3/18/2010 10:49, Aaro Koskinen wrote:
>> The clock used for printk.time=1 does not necessarily start running
>> from zero. On such platforms the bootgraph does not work properly as
>> the calculated boottime will be too long.
> 
> can we fix the platform to be smarter instead ? I'd think that's needed anyway for various
> timers etc to actually work well

Hmm, on OMAP I have gotten so used to this "feature" that I never
thought it was a bug. However, I don't think it will affect anything
else than printk time stamps.

Anyway, I sent a fix proposal to linux-omap list:
http://marc.info/?l=linux-omap&m=126900738712041&w=2

quoted text
>> To correct this, the patch modifies the script to accept only non-zero
>> start times. This ensures the report contains entries only from the
>> period when the clock was running.
>>
>> Signed-off-by: Aaro Koskinen<aaro.koskinen@nokia.com>
> 
> nothing wrong with the patch itself... just sad that it's needed to work around such bugs ;(
> 
> Acked-by: Arjan van de Ven <arjan@linux.intel.com>

I guess we can forget this patch if we agree the platform behaviour is
not correct.

A.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/