From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: value of XIP? and whether it works with 2.6 kernel?
Date: Wed, 25 Aug 2004 09:55:26 +0200 [thread overview]
Message-ID: <20040825075531.ADD00C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 24 Aug 2004 11:44:16 EDT." <Pine.LNX.4.60.0408241141110.6489@localhost.localdomain>
In message <Pine.LNX.4.60.0408241141110.6489@localhost.localdomain> you wrote:
>
> as i read it from david w's post on the MTD list, XIP has limited
> value since flash is noticeably more expensive than RAM anyway.
The fact that flash is more expensive does NOT mean that XIP has no
use. Actually this is nonsense. There are several good reasons why
using XIP may be a good idea. For example, in some security critical
environments users are much more happy to execute code from read-only
storage. Also boot time may be an issue.
> so, thoughts? who's actually using this? and it's not clear from
> the DENX page that there's a patch for the 2.6 kernel -- that page
> refers specifically to 2.4.
We use it on 2.4 with 8xx only (so far).
> anyway, i'm just curious, wondering whether it would be worth giving
> it a try, just for the entertainment value.
Go on...
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
You can observe a lot just by watchin'. - Yogi Berra
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-25 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 15:44 value of XIP? and whether it works with 2.6 kernel? Robert P. J. Day
2004-08-25 7:55 ` Wolfgang Denk [this message]
2004-08-25 11:22 ` Mark Chambers
2004-08-25 15:32 ` Dan Malek
2004-08-25 16:10 ` Mark Chambers
2004-08-25 17:01 ` Dan Malek
2004-08-26 1:27 ` David Woodhouse
2004-08-26 3:45 ` 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=20040825075531.ADD00C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.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 NNTP newsgroup(s).