From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "'Marcin Chrusciel'" <Marcin.chrusciel@cit.be>,
<ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Redboot available RAM
Date: Mon, 19 Jun 2006 07:41:00 -0000 [thread overview]
Message-ID: <006701c69373$c1d0da50$0101010a@netic.com> (raw)
In-Reply-To: <4833790BBC8C1748ABE1E781F17425F30E56F3@citexchange.cit.be>
Marcin,
I had a similar issue that I think I solved by checking on
CYGHWR_HAL_I386_PC_LOAD_HIGH (This option enables building RAM
applications which have a start address outside of the area used by
redboot_GRUB.) The other description says 'Load into higher memory
(2MB)'.
Have you tried that?
...Laurie:{)
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Marcin
Chrusciel
Sent: Monday, 19 June 2006 5:32 PM
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Redboot available RAM
I really stuck on this problem for i386 target. I've searched maillist
several times and found only this thread:
http://sourceware.org/ml/ecos-discuss/2006-04/msg00184.html
Which is about exactly the same problem as I have.
I tried also both types of discovering available RAM - bios and
hardcoding. No results. All I need is about 1MB for application...
Thanks in advance for any help
Marcin
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
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:[~2006-06-19 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:32 Marcin Chrusciel
2006-06-19 7:41 ` Laurie Gellatly [this message]
2006-06-19 8:17 Marcin Chrusciel
2006-06-19 8:19 Marcin Chrusciel
2006-06-19 8:24 ` Laurie Gellatly
2006-06-20 8:12 Marcin Chrusciel
2006-06-20 8:50 ` 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='006701c69373$c1d0da50$0101010a@netic.com' \
--to=laurie.gellatly@netic.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).