From: Jamie Guinan <guinan@bluebutton.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: Linux Filesystem Access
Date: Wed, 30 Jun 1999 11:55:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.990630145121.18905A-100000@newt.home.net> (raw)
In-Reply-To: <Pine.LNX.3.96.990630131115.18787A-100000@newt.home.net>
On Wed, 30 Jun 1999, Jamie Guinan wrote:
> Actually, I found that the stuff from syscall-i386-linux-1.0.S
> works well enough for me. I am able to open and write files
> with code such as,
...
> I have yet to try reading, though.
Hm, cyg_sys_hal_read() seems to block eCos entirely. Guess
I have some more thinking to do.
What I would like to do is block on a read() from some external
source under eCos/synthetic-linux. This way I can test code
that will eventually read from a serial port on my embedded
PowerPC target.
-Jamie
prev parent reply other threads:[~1999-06-30 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-21 5:53 [ECOS] linux .rel.got problem Andrew Lunn
1999-06-21 6:10 ` Jesper Skov
1999-06-21 7:11 ` Jesper Skov
1999-06-28 22:48 ` Jamie Guinan
1999-06-29 0:26 ` Jesper Skov
1999-06-28 13:07 ` Jamie Guinan
1999-06-28 14:00 ` Jonathan Larmour
1999-06-30 10:49 ` [ECOS] Linux Filesystem Access Jamie Guinan
1999-06-30 11:55 ` Jamie Guinan [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=Pine.LNX.3.96.990630145121.18905A-100000@newt.home.net \
--to=guinan@bluebutton.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).