From: Wolfgang Denk <wd@denx.de>
To: christof <xfr@freenet.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kernel executing from flash
Date: Tue, 28 Mar 2000 13:40:14 +0200 [thread overview]
Message-ID: <200003281140.NAA05466@denx.local.net> (raw)
In-Reply-To: Your message of "Tue, 28 Mar 2000 12:30:06 +0200." <38E089AD.F415DCB7@freenet.de>
In message <38E089AD.F415DCB7@freenet.de> you wrote:
>
> My primary aim is not to gain speed or to save money, although this is
> important for my application too.
> By fetching opcodes from flash I expect more stability in temperature- and
> emc-critical environement, for data in "ROM" is saver than in RAM. Of corse,
> there is always run-time critical data in RAM (processor stack), but the
> probability of "irrepairable" errors should decrease by runnig from flash.
A crash is a crash is a crash...
If you have memory errors, your system is bound to crash sooner or
later, no matter if it hits the program code, or the stack, or data.
What's the difference between a crash because of a bad opcode or one
because of a division by zero because of faulty data?
Black magic...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Work 8 hours, sleep 8 hours; but not the same 8 hours.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-28 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-23 15:14 kernel executing from flash christof
2000-03-23 16:33 ` Markus Sundberg
2000-03-23 20:05 ` Wolfgang Denk
2000-03-24 9:54 ` Rob Taylor
2000-03-28 10:30 ` christof
2000-03-28 11:40 ` Wolfgang Denk [this message]
[not found] <200003241749.MAA00739@misery.wavemark.com>
2000-03-27 8:54 ` Rob Taylor
2000-03-28 0:04 ` Graham Stoney
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=200003281140.NAA05466@denx.local.net \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=xfr@freenet.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.