--- In Lennert Buytenhek <> wrote:
>
> Hi!
>
> You can't catch the interrupt from userspace, the only way to handle
> it is to write a small kernel driver (which then perhaps passes the
> interrupt to userspace.) I can whip something like this up if
you're
> interested, what kernel version are you using?
>
Hi,
thanks for your reply. I'm using kernel version 2.4.26-ts9 and I
would realy appreciate your help. Since I'm new to both Linux and
embedded I find it hard to use some guides and tutorials since I
don't know whether it applies to Linux on ARM or Linux on x86.
> It's likely that the version of linux you use uses timer 1 for the
> periodic (10ms) timer interrupt, so when you reprogram it, the time
> of day will run faster or slower than usual, which can confuse a
> lot of things in the system..
>
>
> --L
>
That explains the behaviour. Maybe its better to use timer 2 then.
The longest time span needed will be 1 second so timer 3 seems to be
overkill and timer 4 doesn't trigger interrupts if I read the user
guide correct.
I didn't recieve this answer in my mail box as usual. Strange!
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|