From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: Bart Veer <bartv@ecoscentric.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] hal_delay_us() patch to at91_misc + multithreading
Date: Mon, 13 Jun 2005 17:57:00 -0000 [thread overview]
Message-ID: <1118685436.31409.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20050611134933.7C2CA65C057@smtp.ecoscentric.com>
> I would like to see the macro
> definition upgraded to make it compulsory rather than optional, and
> require the macro to be thread-safe.
Makes sense. I2C seems to be based upon these assumptions.
> I am happy to do a synthetic
> target implementation, but that still leaves other architectures where
> the macro would need to be added or fixed.
How about calibrating a CPU counter loop implementaiton upon startup
using the default hardware timer in the HAL?
- a couple of ms to the startup time is a small price to pay for
a default implementation of a HAL_DELAY_US()
- The HAL_DELAY_US() definition should state that the the accuracy
is not very good, but that it is guaranteed to wait at least
n us.
Is there a fundamental reason why HAL_DELAY_US() needs to be very
accurate(i.e. say <20-30%)
>
> Bart
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-13 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 11:24 Øyvind Harboe
2005-06-11 13:49 ` Bart Veer
2005-06-13 17:57 ` Øyvind Harboe [this message]
2005-06-13 18:54 ` Bart Veer
2005-06-15 6:22 ` Øyvind Harboe
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=1118685436.31409.9.camel@localhost.localdomain \
--to=oyvind.harboe@zylin.com \
--cc=bartv@ecoscentric.com \
--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).