From: Philippe Gerum <rpm@xenomai.org>
To: Thomas Kuhlmann <maillist@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] what should __adeos_set_timer(hz) do?
Date: Tue, 29 Jun 2004 13:15:09 +0200 [thread overview]
Message-ID: <1088507709.636.14.camel@domain.hid> (raw)
In-Reply-To: <200406291242.32834.maillist@domain.hid>
On Tue, 2004-06-29 at 12:42, Thomas Kuhlmann wrote:
> Hello,
>
> based on the adeos-linux-2.4.22-armnommu-r12.patch for uClinux 2.4.22-uc0 from
> http://download.gna.org/adeos/patches/v2.4/armnommu/ I'm trying to extend
> (port) this patch for armnommu/arch-netarm/ (NetSilicon NS7520 processor).
>
> Has anybody tried a patch for armnommu/arch-netarm (just to prevent me doing
> it again)?
>
> The function __adeos_set_time(unsigned long hz) has to be ported to netarm.
> However what should it do?
> In the given patch for the armnommu/arch-atmel/ it looks like the kernel timer
> is disabled, the frequency is changed, and the timer is enabled again (not
> one shot, but periodic mode). Is this the correct semantics of
> __adeos_set_timer(hz)?
>
Strictly speaking, setting the hw timer in periodic mode is not required
by Adeos. __adeos_set_timer() is a helper for the adeos_tune_timer()
service that is expected to set the Linux timer hw to a given frequency.
This helper is totally ARM-dependent and does not even exist for other
archs.
> Sorry if my question is misplaced here and I'd better contact the ARM
> responsible persons (let me know of this).
>
Your question indeed belongs to this list. Maybe the ARM guru (who I'm
not) is listening?
> Thanks, Thomas.
--
Philippe.
prev parent reply other threads:[~2004-06-29 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 10:42 [Adeos-main] what should __adeos_set_timer(hz) do? Thomas Kuhlmann
2004-06-29 11:15 ` Philippe Gerum [this message]
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=1088507709.636.14.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=maillist@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.