From: Bart Veer <bartv@redhat.com>
To: rob.wj.jansen@philips.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] File IO under Linux synthetic target
Date: Wed, 30 May 2001 08:13:00 -0000 [thread overview]
Message-ID: <200105301513.f4UFDE702510@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <0056890030837858000002L982*@MHS>
>>>>> "Rob" == rob wj jansen <rob.wj.jansen@philips.com> writes:
Rob> I'm using a ROM filesystem on my target (ARM710T) but want to
Rob> do some testing/debugging of the application on a linux
Rob> target.
Rob> Is File I/O on the linux target supported / which package(s)
Rob> do I need= ?
File I/O is not yet available on the synthetic target - at least, not
using the eCos functionality. With the current release sources it is
possible to make some Linux system calls to perform file I/O, for
example by calling cyg_hal_sys_open() and cyg_hal_sys_read(), but
obviously those will have the Linux semantics rather than the eCos
ones.
Bart
next prev parent reply other threads:[~2001-05-30 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 8:05 rob.wj.jansen
2001-05-30 8:13 ` Bart Veer [this message]
2001-05-31 7:30 rob.wj.jansen
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=200105301513.f4UFDE702510@sheesh.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=rob.wj.jansen@philips.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).