From: Kent Borg <kentborg@wavemark.com>
To: jgreen@mvista.com
Cc: fray@mvista.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Running from ROM
Date: Tue, 6 Jun 2000 09:39:47 -0400 [thread overview]
Message-ID: <200006061339.JAA30741@rome.wavemark.com> (raw)
In-Reply-To: <00060516034300.24189@minotaur.mvista.com> (message from Joe Green on Mon, 5 Jun 2000 15:21:14 -0700)
Joe Green <jgreen@mvista.com> wrote:
>The project Mark mentioned is specifically for running the kernel
>from ROM.
That doesn't sound horribly complicated. Groady details to be sure,
but ~conceptually~ easy.
>Are you also asking about running application code from ROM?
Yes. I realize that it can frequently make sense to compress and load
into RAM, but there is a significant chance that running directly from
ROM could be sensible for us. Interestingly, part of the reason might
be a "real space" approach, that is, wanting to be deterministic about
whether a given operation can successfully run. In a system where
sometimes every byte of RAM is needed, I can imagine circumstances
where, depending on the order of operations, some RAM-hungry
operations could sometimes fail and sometimes succeed. Getting one
more "it's virtual, it does the right thing"-aspect out of the system
could help. Or maybe not.
So back to the question, it appears there are not scads of people
already doing this. Suggestions on approaches? As I let my
imagination run only ugly solution fragments come out on this.
Thanks,
-kb, the Kent who needs to keep reading Rubini's book to learn more
about how the normal case works.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-06 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 21:37 Running from ROM Kent Borg
2000-06-05 22:03 ` Mark Hatle
2000-06-05 22:21 ` Joe Green
2000-06-06 13:39 ` Kent Borg [this message]
2000-06-06 14:12 ` Tom Montgomery
2000-06-06 18:05 ` Dan Malek
2000-06-06 20:11 ` Kent Borg
2000-06-06 21:04 ` Dan Malek
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=200006061339.JAA30741@rome.wavemark.com \
--to=kentborg@wavemark.com \
--cc=fray@mvista.com \
--cc=jgreen@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).