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: Wed, 15 Jun 2005 06:22:00 -0000 [thread overview]
Message-ID: <1118816539.11778.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20050613185448.1D92265C057@smtp.ecoscentric.com>
[lots of valid objections to my suggested HAL_DELAY_US() implementation
deleted]
There is one issue with making HAL_DELAY_US() compulsory that has not
been discussed: how likely is it to get a consensus to do so?
My thinking was that a default implementation of HAL_DELAY_US() would
improve that chances of getting a consensus.
The crummy HAL_DELAY_US() I suggested scored on this point. It would
work correctly on almost any platform.
--
Øyvind Harboe
http://www.zylin.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-06-15 6:22 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
2005-06-13 18:54 ` Bart Veer
2005-06-15 6:22 ` Øyvind Harboe [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=1118816539.11778.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).