From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] FreeBSD stack broken when systick != 10ms
Date: Sun, 19 Jan 2014 18:08:00 -0000 [thread overview]
Message-ID: <lbh49q$a90$1@ger.gmane.org> (raw)
It appears that the FreeBSD stack is still hard-wired to work only
with a system tick of 10ms. Has anybody gone through it to see how
much work it would take to make the system tick time something that
could be configured at build time using ecosconfig?
Does the LWIP stack work with system ticks other than 10ms?
--
Grant Edwards grant.b.edwards Yow! I'm having BEAUTIFUL
at THOUGHTS about the INSIPID
gmail.com WIVES of smug and wealthy
CORPORATE LAWYERS ...
--
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 reply other threads:[~2014-01-19 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 18:08 Grant Edwards [this message]
2014-01-19 19:01 ` [ECOS] " Grant Edwards
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='lbh49q$a90$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).