All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Hendricks" <ra6353@email.sps.mot.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Another try at the run-from-Flash issue for MPC8xx/MBX/custom
Date: Thu, 30 Mar 2000 14:39:19 -0600	[thread overview]
Message-ID: <38E3BB77.890DB46D@email.sps.mot.com> (raw)
In-Reply-To: 38E27471.83CCAC10@innocon.com


Doug,
  Do you have the I-Cache enabled when decompressing?  What about
disabling serialization? (Set ICTRL to 0x7)

Doug Rogers wrote:
>
> I, too, would like to run from Flash. The question for me isn't speed,
> isn't cost, nor EMI effects. It is simply a matter of size. We have a
> very small area in which to squeeze the parts, and the best we could do
> is 32M RAM and 16M ROM. Our application code is in the 10M range (text
> only, even after chopping over half of it out!), but it is expected to
> grow. So for us it's not really a matter of cost or (running) speed,
> since the Flash runs fast enough for our purposes.
>
> As another constraint, our card needs to be able to run very soon after
> power-up. I've hacked the LynxOS startup monitor to detect either gzip'd
> or bzip2'd KDI's. I've timed the decompression of our smaller test image
> and it takes over 40 seconds on a 40MHz MBX860 board. That's too slow.
> We could live with 20, perhaps, but not much more than that. For now I
> boot my images over the network since our MBX board has only 4M Flash.
> It's faster than decompressing!
>
> With LynxOS, we're able to keep in Flash both the text sections of the
> kernel AND of all binaries on the filesystem. Wow! That allows us to put
> only the RAM disk and vector/data/bss sections into RAM. Shweet!
>
> I was hoping that Linux was to that point, but apparently not. Just
> having the kernel run from ROM would be helpful for now, so if anyone
> out there has done so, I'd be very appreciative of any feedback.
>
> Thanks!
>
> Doug
>
> --
> --_._-__-____------_--_-_-_-___-___-____-_--_-___--____-___--_-__--___-_
> Doug Rogers, ICI   | The strongest reason for the people to retain the
> V:703.893.2007x220 | right to keep and bear arms is, as a last resort,
> www.innocon.com    | to protect themselves against tyranny in
> ___________________| Government. [Thomas Jefferson]
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-03-30 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-29 21:24 Another try at the run-from-Flash issue for MPC8xx/MBX/custom Doug Rogers
2000-03-30  1:25 ` Dan Malek
2000-03-30  8:51 ` Markus Sundberg
2000-03-30 20:39 ` Richard Hendricks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-30 14:56 Brown, David (dbrown03)
2000-03-30 15:24 ` 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=38E3BB77.890DB46D@email.sps.mot.com \
    --to=ra6353@email.sps.mot.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 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.