From: Vlasios Tsiatsis <tsiatsis@ee.ucla.edu>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Assabet real time clock resolution
Date: Mon, 11 Dec 2000 16:20:00 -0000 [thread overview]
Message-ID: <3A356F43.4A6CDC04@ee.ucla.edu> (raw)
Hi,
i want to change the real time clock resolution from 100 ticks/sec to
1000 ticks/sec for
eCos running on an Assabet board. I am developing eCos on a Linux
machine
so i have to manually configure eCos if necessary.
I noticed that i cannot change the ecos.ecc (configuration file) because
the real time clock resolution is not modifiable by the user.
So i tried to obtain a handle to the real time clock and change the
resolution
inside cyg_user_start() but the resolution remains the same.
Is it a limitation of the board or am i doing something wrong ?
thanks,
vlasios
next reply other threads:[~2000-12-11 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 16:20 Vlasios Tsiatsis [this message]
[not found] <3A37E2C3.199576AE@ee.ucla.edu>
2000-12-13 13:06 ` Gary Thomas
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=3A356F43.4A6CDC04@ee.ucla.edu \
--to=tsiatsis@ee.ucla.edu \
--cc=ecos-discuss@sources.redhat.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).