public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alex Mathews <alexma@crosstor.com>
To: "Boris V. Guzhov" <borg@int.spb.ru>
Cc: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Significant updates to Red Hat eCos
Date: Tue, 29 Aug 2000 07:18:00 -0000	[thread overview]
Message-ID: <39ABC71D.2D1FD3F0@crosstor.com> (raw)
In-Reply-To: <009601c011c0$28cdc1a0$7601a8c0@borg>

Information about POSIX synchronization support can be found at
http://sources.redhat.com/ecos/docs-latest/ecos-elix/ecos-elix.2.html#pgfId=2626832 .

For future reference check out the current POSIX information under the
eCos EL/IX documentation at
http://sources.redhat.com/ecos/docs-latest/ecos-elix/ecos-elix.1.html .

-Alex

"Boris V. Guzhov" wrote:
> 
> There are some questions.
> 
> - Is there in new updates  a support of POSIX recursive mutex's
> (PTHREAD_MUTEX_RECURSIVE)?
> -  Is there a support of   POSIX rwlock's?
> If isn't present, whether  will it be added in the following versions?
> 
> Thanks in advance.
> 
> --
> Boris Guzhov,
> St.Petersburg, Russia
> 
> >
> > Red Hat is pleased to announce a series of significant additions and
> > updates to eCos, the Embedded Configurable Operating System. As an Open
> > Source company, Red Hat has made these improvements available from the
> > development repository available via anonymous CVS ( see
> > http://sources.redhat.com/ecos/anoncvs.html ).
> > <skipped> ...

-- 
Alex Mathews
CrosStor Software, Inc.
908-226-0100 ext 148
alexma@crosstor.com

  reply	other threads:[~2000-08-29  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-25 10:33 Jonathan Larmour
2000-08-25 13:12 ` Jonathan Larmour
2000-08-29  6:57 ` Boris V. Guzhov
2000-08-29  7:18   ` Alex Mathews [this message]
2000-08-29  9:37   ` Jonathan Larmour
2000-09-12  2:24 ` [ECOS] " Dataton postmaster

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=39ABC71D.2D1FD3F0@crosstor.com \
    --to=alexma@crosstor.com \
    --cc=borg@int.spb.ru \
    --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).