Hi,
> btw. is there an overflow in the calculation for the clocking?
>
> root:/> cat /proc/cpuinfo
> CPU: lm32
> MMU: none
> FPU: none
> Clocking: 88.9MHz
> BogoMips: 3578.26
> Calibration: 1789132800 loops
Yes,
Clocking should be 2236.416MHz. :)
Takeshi
__
Hi,
Am Monday 25 January 2010 09:43:35 schrieb Takeshi MATSUYA:
> Bogo Mips and calibration infomation are incorrect.
> UART is not used for its calculation.
> It seems there are problems with the timer or interrupt controller.
whoops typo, it should read "milkymist,sysctl.frequency"
The interru
Hi, Michael
On 2010/01/25, at 7:27, Michael Walle wrote:
> after i fixed some interrupt handling stuff (basically the interrupts never
> gots desasserted interally) the output from userspace to the UART is really
> slow. The kernel messages are processed normally.
>
> It seems, that one charact
Hi,
On 2010/01/25, at 16:57, Michael Walle wrote:
>
> With the HEAD of the qemu-lm32 milkymist branch? Right after the kernel
> spwans init, you should see, that the output gets printed really slow on
> the console. Please also try to slow down the timer frequency to 10MHz by
> passing the option
Am Mo, 25.01.2010, 07:17, schrieb Takeshi MATSUYA:
> When I tested the following commands, it took about 100 millisecond.
> It seems like there is no problem.
> What test did you do?
>
> root:/> ls -la /etc/services
> -rw-r--r--1 root root 8205 Feb 6 2008 /etc/services
> roo
Hi,Michael
On 2010/01/25, at 7:27, Michael Walle wrote:
> the output from userspace to the UART is really slow.
> The kernel messages are processed normally.
>
> It seems, that one character needs one timer tick until it gets passed to the
> UART hardware.
>
> Takeshi, can you have a quick look a
Hi,
after i fixed some interrupt handling stuff (basically the interrupts never
gots desasserted interally) the output from userspace to the UART is really
slow. The kernel messages are processed normally.
It seems, that one character needs one timer tick until it gets passed to the
UART hard
