From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Richard Cochran <richard.cochran@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Porting to Intel IXP425
Date: Fri, 30 Mar 2007 16:05:38 +0200 [thread overview]
Message-ID: <460D1932.5010305@domain.hid> (raw)
In-Reply-To: <899865CA54E4444DAF2E3639C04C5F4805EC5F@trillian.at.omicron.at>
Richard Cochran wrote:
>>Right. And I think the IXP425 has no cascaded IRQ, so you can define
>>__ipipe_mach_irq_mux_p to 0, and do not have to implement
>>__ipipe_mach_demux_irq.
>
>
> That was easy.
>
> (The IXP425 has no cascaded interrupts.)
>
> Now, about the rest, by reading the other arm ports, I learned the
> following:
>
> __ipipe_mach_get_dec()
>
> Returns the periodic timer interval in HW ticks.
>
> __ipipe_mach_set_dec()
>
> Sets the periodic timer interval.
The timer is aperiodic (most of the time) when running Xenomai, so
__ipipe_mach_set_dec is called for each timer tick and programs the
timer hardware for the next tick.
>
> __ipipe_mach_get_tsc()
>
> Returns the free flowing time stamp register as a 64 bit integer.
>
> __ipipe_mach_acktimer()
>
> Called by the timer ISR, clears the timer interrupt.
>
> __ipipe_mach_release_timer()
>
> Restores the timer interval to the value expected by Linux.
__ipipe_mach_release_timer is called when Xenomai stops handling the
timer and let Linux handle it.
--
Gilles Chanteperdrix
next prev parent reply other threads:[~2007-03-30 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 10:20 [Adeos-main] Porting to Intel IXP425 Richard Cochran
2007-03-30 11:35 ` Sebastian Smolorz
2007-03-30 12:16 ` Gilles Chanteperdrix
2007-03-30 13:51 ` Richard Cochran
2007-03-30 14:05 ` Gilles Chanteperdrix [this message]
2007-03-30 14:33 ` Richard Cochran
2007-03-30 14:41 ` Gilles Chanteperdrix
2007-03-30 21:29 ` [Adeos-main] " Schlägl Manfred jun.
2007-03-31 10:33 ` Gilles Chanteperdrix
2007-03-30 14:55 ` [Adeos-main] " Philippe Gerum
2007-03-30 16:07 ` Richard Cochran
2007-03-30 17:16 ` Gilles Chanteperdrix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=460D1932.5010305@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adeos-main@gna.org \
--cc=richard.cochran@domain.hid \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.