public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: Micha&lstrok; Ole&nacute;czuk <olenczuk@rts.com.pl>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] clock resolution
Date: Mon, 23 Apr 2001 05:50:00 -0000	[thread overview]
Message-ID: <XFMail.20010423065009.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <014701c0cbfa$f80f7900$1e00a8c0@OLENCZUK>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On 23-Apr-2001 Micha³ Oleñczuk wrote:
> Hi,
> I am beginner in eCos programming and I have some problems:
> 
> I want to set real time clock resolution to 1000 ticks/sec (or higher). Is
> it available to set it from software using cyg_clock_set_resolution() ?
> Setting dividend and divisor in cyg_resolution_t structure gives no effect
> (cyg_clock_get_resolution() gives the same before-setting resolution value
> =100).
> I changed it in eCos ConfigTool, and after calling
> cyg_clock_get_resolution() I got my setted resolution resolution, but some
> function like cyg_thread_delay() or alarm functions work the same as with
> default resolution value.

How do you mean "worked the same"?  cyg_thread_delay() takes a number of 'ticks'
as it's argument, so the only way to see if the value changes is by using some
outside observation (measure against a wall clock, for example).

> 
> How to get 1000 or more ticks for a second ????

What platform are you using?

  reply	other threads:[~2001-04-23  5:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23  5:40 Micha&lstrok
2001-04-23  5:50 ` Gary Thomas [this message]
2001-04-23 11:10 ` Jonathan Larmour

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=XFMail.20010423065009.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).