From: Jonathan Larmour <jlarmour@redhat.com>
To: dorai@sasken.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] problem in using cyg_hal_sys_read
Date: Fri, 09 Feb 2001 09:42:00 -0000 [thread overview]
Message-ID: <3A842BF2.BE116C28@redhat.com> (raw)
In-Reply-To: <3A828DD3.DBD35179@sasken.com>
Dorairaj V wrote:
>
> Hi ,
> I'm using the ecos api cyg_hal_sys_read() to read from a named pipe in
> a linux based synthetic target (ecos 1.3.1 on i386 linux RHL 6.2 ) . I
> find that cyg_hal_sys_read fails and returns error number -4 .
> Can some one let me know what does the error code mean ? Also where can
> I get a comprehensive list of ecos error codes and their meanings .
This isn't an eCos error code, it's a linux kernel error code, and
correlates with what is in /usr/include/asm/errno.h. So -4 would be EINTR,
which means you probably ctrl-C'd the app.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
prev parent reply other threads:[~2001-02-09 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 4:11 Dorairaj V
2001-02-09 9:42 ` Jonathan Larmour [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=3A842BF2.BE116C28@redhat.com \
--to=jlarmour@redhat.com \
--cc=dorai@sasken.com \
--cc=ecos-discuss@sourceware.cygnus.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).