From: Andrew Lunn <andrew@lunn.ch>
To: Dohun Kim <hunkim@postech.ac.kr>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] [Q] Redboot's FAT16 functions
Date: Thu, 08 Jul 2004 13:49:00 -0000 [thread overview]
Message-ID: <20040708134929.GF18802@lunn.ch> (raw)
In-Reply-To: <20040708.AAA1089294090@postech.ac.kr>
On Thu, Jul 08, 2004 at 10:42:35PM +0900, Dohun Kim wrote:
>
> Dear ecos users,
>
> Is there any one who has FAT16 open and read functions
> in Redboot?
>
> If you could send a function file or inform me of
> its information, I would appreciate it.
I beleave Savin Zlobec is working on this. At least he is making the
fat32 code not depend on the kernel, which is a big step towards being
able to read FAT32 files in redboot.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-07-08 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 13:42 Dohun Kim
2004-07-08 13:49 ` Andrew Lunn [this message]
2004-07-08 14:06 ` Nick Garnett
[not found] <20040708.AAA1089296074@postech.ac.kr>
2004-07-08 14:49 ` Nick Garnett
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=20040708134929.GF18802@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=hunkim@postech.ac.kr \
/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).