public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@ecoscentric.com>
To: "Marcin Chrusciel" <Marcin.chrusciel@cit.be>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Redboot available RAM
Date: Tue, 20 Jun 2006 08:50:00 -0000	[thread overview]
Message-ID: <m3bqsoqkha.fsf@xl5.calivar.com> (raw)
In-Reply-To: <4833790BBC8C1748ABE1E781F17425F30E572C@citexchange.cit.be>

"Marcin Chrusciel" <Marcin.chrusciel@cit.be> writes:

> Laurie,
> 
> Yesterday I tried your tip, but it didn't help in my case. I will
> explain how I do it:
> 
> I take i386 Realtek template, choose redboot in packages, then I go to
> eCos HAL -> i386 architecture -> I check Load into higher memory (I
> accept solutions for conflicts) and then I go for Startup type - I
> change it for floppy and I get a conflict that I should use GRUB, but I
> discard a solution so it stays Floppy. It builds fine and image starts
> properly but still the same amount of available RAM appears (about 64k) 
> 
> Any ideas??? Thanx;)

FLOPPY startup will only load into the bottom 640K and will only use
memory in that area. It is really only intended for use with RedBoot,
although applications that can live in 640K will work too.

To run applications above 1M either load RAM startup applications with
a FLOPPY RedBoot, use a GRUB-loaded RedBoot to load them, or load the
application directly using a GRUB startup type.


-- 
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:[~2006-06-20  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  8:12 Marcin Chrusciel
2006-06-20  8:50 ` Nick Garnett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-19  8:19 Marcin Chrusciel
2006-06-19  8:24 ` Laurie Gellatly
2006-06-19  8:17 Marcin Chrusciel
2006-06-19  7:32 Marcin Chrusciel
2006-06-19  7:41 ` Laurie Gellatly

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=m3bqsoqkha.fsf@xl5.calivar.com \
    --to=nickg@ecoscentric.com \
    --cc=Marcin.chrusciel@cit.be \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).