public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: Savin Zlobec <savin@elatec.si>
Cc: jam2000@pisem.net, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: building redboot with eCos kernel
Date: Fri, 21 May 2004 16:18:00 -0000	[thread overview]
Message-ID: <m3brkhj00n.fsf@miso.calivar.com> (raw)
In-Reply-To: <40AE0F3F.7080604@elatec.si>

Savin Zlobec <savin@elatec.si> writes:

> Nick Garnett wrote:
> 
> >Michael Jastrebtsoff <jam2000@pisem.net> writes:
> >
> >> Hello, All.
> >> I need to build Redboot with FAT support. But FAT requires eCos
> >> kernel.
> >> I try build Redboot with eCos kernel, but this don't work.(when i
> >> connected to redboot via terminal, i'v  got a random chars on screen.)
> >
> >The FAT filesystem will not work in RedBoot since it requires too many
> >kernel facilities to work. You cannot put the kernel into RedBoot
> >since RedBoot is intended to be a stand alone application, there are
> >just too many assumptions for this to work.
> >
> There shouldn't be a lot do to get fatfs into RedBoot - all I can think of
> right now is the cyg_mempool_* api which is not available in nonkernel
> configurations.
> 
> >The only use that RedBoot would have for FAT filesystem support is to
> >load executables. So a simple read-only loader similar to the one that
> >already exists for ext2 would be a better solution.
> >
> This has already beed done - check The DODES project at
> http://www.m17n.org/dodes/ecos/index.en.html.

Give or take a bit of fixing to bring it up to date -- it is 2.5 years
old -- that is what I meant. It's a pity it has never been contributed
back to the public repository.

However, the main point is that putting the whole FAT fs into RedBoot
is overkill when RedBoot can only use it for read-only access. We need
to do our best to keep RedBoot small.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2004-05-21 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-21 15:03 Savin Zlobec
2004-05-21 16:18 ` Nick Garnett [this message]
2006-05-31  0:14 [ECOS] Building redboot with eCos Kernel Andre-John Mas
2006-05-31  3:09 ` [ECOS] " Grant Edwards
2006-06-01  1:51   ` André-John Mas

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=m3brkhj00n.fsf@miso.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jam2000@pisem.net \
    --cc=savin@elatec.si \
    /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).