public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: jlarmour@cygnus.co.uk (Jonathan Larmour)
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] linux .rel.got problem
Date: Mon, 28 Jun 1999 14:00:00 -0000	[thread overview]
Message-ID: <7l8n2c$muo$1@korai.cygnus.co.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.990628160234.16277A-100000@newt.home.net>

In article < Pine.LNX.3.96.990628160234.16277A-100000@newt.home.net >,
Jamie Guinan  <guinan@bluebutton.com> wrote:
>
>Before I apply the patch from CVS (thanks Jesper), is fopen()/fgets()
>implemented for normal files under the Linux synthetic target?

Fraid not.

>If not, would a simple "linux filesystem driver" be worth spending
>some time on?

We do have plans for an all-singing all-dancing configurable pluggable
virtual file system infrastructure :-), but it'll take some time to sort
out. Expect an RFC in the not-too-distant future. But if you want to hack
something quick and dirty up, feel free!

If you surround it by ifdefs for now, that'll make it nice and easy to find.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  reply	other threads:[~1999-06-28 14:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-21  5:53 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 [this message]
1999-06-30 10:49     ` [ECOS] Linux Filesystem Access Jamie Guinan
1999-06-30 11:55       ` [ECOS] " Jamie Guinan

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='7l8n2c$muo$1@korai.cygnus.co.uk' \
    --to=jlarmour@cygnus.co.uk \
    --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).