From: Nick Garnett <nickg@ecoscentric.com>
To: <kevin_lemay@agilent.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] i386 Memory Size Problem
Date: Wed, 03 Dec 2003 10:29:00 -0000 [thread overview]
Message-ID: <m34qwiw5y7.fsf@miso.calivar.com> (raw)
In-Reply-To: <1BEBA5E8600DD4119A50009027AF54A010FAE48A@axcs04.cos.agilent.com>
<kevin_lemay@agilent.com> writes:
> It appears that Linux uses hard coded memory addresses to store the
> memory map and size, switches to protected mode and then accesses
> the saved data in ram.
>
> I attempted to use this same method, but it does not appear to be
> running. I added new character outputs to the display during boot
> which do not appear. Any ideas on what I am doing wrong?
Maybe you have chosen some inconvenient addresses. Does the
application work if it does not access the saved memory sizes, just
uses the CMOS values? You mentioned previously that you were putting
the sizes at 1Mb and that it worked, what have you changed since then?
Make sure that your debug outputs are not corrupting things
themselves.
I'm not sure what else I can suggest.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-12-03 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 20:13 kevin_lemay
2003-12-03 10:29 ` Nick Garnett [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-25 22:24 kevin_lemay
2003-11-26 11:45 ` Nick Garnett
2003-11-25 16:30 kevin_lemay
2003-11-25 17:29 ` Nick Garnett
2003-11-24 22:53 kevin_lemay
2003-11-25 10:57 ` 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=m34qwiw5y7.fsf@miso.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=kevin_lemay@agilent.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).