From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: "Brown, David (dbrown03)" <DBrown03@harris.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Questions about 8xxrom
Date: Mon, 29 May 2000 17:48:15 -0400 [thread overview]
Message-ID: <3932E59F.4A3F4936@embeddededge.com> (raw)
In-Reply-To: 20000529022507.5F4463C9DF@elph.research.canon.com.au
Graham Stoney wrote:
> > After all that, it still fails, while decompressing initrd.
I must have missed this.....what is the error? Post the few lines
that show the actual/relocated debug messages for the zImage portions.
> I suspect Dan's comments last week explain that this doesn't currently work:
The word "currently" is quite correct. It was never designed to
decompress directly from Flash.
> Dan, any chance you could clarify what would need to be done in order to
> decompress the initrd directly from flash? We also want to do this
> eventually, and would like to avoid the wasted copy to RAM.
Nothing needs to be done. The code in arch/ppc/mbxboot/misc.c will
allocate a RAM area and copy the initrd from Flash to RAM. The address
and size of this is given to the kernel when it is started.
The functions for uncompressing and using initrd are part of the kernel
and common to all architectures. It assumes the initrd is in RAM,
which is also common to all architectures. I don't intend to change
this, and I don't see any real reason either. The product dependent
boot will place a copy of initrd in RAM, which could be from a network,
CDROM, Floppy, Flash ROM, PCMCIA disk, etc. The kernel isn't responsible
for placing it there, only for using it. It is a common feature for
all systems, and thankfully someone made it real easy for us to use it.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-29 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-26 13:48 Questions about 8xxrom Brown, David (dbrown03)
2000-05-26 16:11 ` Dan Malek
2000-05-29 2:25 ` Graham Stoney
2000-05-29 21:48 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-30 13:35 Brown, David (dbrown03)
2000-05-30 17:41 ` Dan Malek
2000-06-01 6:49 Duncan Palmer
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=3932E59F.4A3F4936@embeddededge.com \
--to=dan@netx4.com \
--cc=DBrown03@harris.com \
--cc=greyham@research.canon.com.au \
--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).