|
Hello Alejandro, I've also seen the same for my system when calling the command 'uptime'. It's exactly two times too fast. (I think to have been reporting this a while ago.) So I guess the factor 2 could be a bug in the driver, but didn't had the time until know to dig for it. Have a nice weekend, Andreas. Andreas Roland Murwiesenstr. 47 8057 Zürich Switzerland, Tel: +41-1-313 12 16 Mobile: +41-78 656 0 323 Email: arol'#'wolke7.net alucero@os3sl.com wrote: ___________________________ microblaze-uclinux mailing list microblaze-uclinux@itee.uq.edu.au Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/I have problems with the timer configuration at arch/microblaze/kernel/microblaze_timer.c The value for CONFIG_XILINX_CPU_CLOCK_FREQ is 100000000, although the use of DCM in the FPGA design changes the clock signal to 75000000. If the systems boots with the original value, the timer goes faster than expected: a minute is not 60 seconds but 80s. As I know the 100 should be 75, so I have changed it, and instead of the behaviour expected the timer is now running two times faster than expected. After studying the code and the timer documentation, the configuration seems to be ok for me. So I don't know what is happening. However, if I set the CONFIG_XILINX_CPU_CLOCK_FREQ to 150000000 the timer works fine. Can any one show me the light? Thanks. |