From: Peter Desnoyers <pdesnoyers@chinook.com>
To: Rudolf Ladyzhenskii <rudolf.ladyzhenskii@act-aus.net>
Cc: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: autoboot with initial RAM disk
Date: Fri, 21 Dec 2001 11:01:44 -0500 [thread overview]
Message-ID: <3C235CE8.2E5E723C@chinook.com> (raw)
In-Reply-To: B164B53F5BD6D511888D009027732E1A0249CB@ntserver.act.domain
(this really belongs on the ppcboot list...)
You can do arbitrarily complicated things in the ppcboot 'bootcmd'
argument. In your case:
setenv bootcmd tftp 100000 pImage\; tftp 300000 initrd\; bootm 100000
300000
If your bootcmd variable gets too long, ppcboot will complain - then you
just have to do something like:
setenv bootcmd run first_half\; run second_half
setenv first_half command\; command\; ...
setenv second_half ...
Rudolf Ladyzhenskii wrote:
>
> Hi, all
>
> I am using ppcboot to start my 8260 based card. At the moment, we load Linux
> kernel via tftp and then start it. Linux kernel maps its root file system
> over the network. This works fine qith ppcboot autoboot feature.
>
> Now, we want to put initial RAM disk into RAM as well as compressed kernel.
> Do do that, both images have to be copied into card's memory using tftp and
> them bootm command will be used with two arguments to start kernel.
>
> To continue to use ppcboot autoboot feature we have to pass two commands as
> boot command (to tftp two kernels) and then issue bootm command with two
> arguments. Is there any way of doing it without altering the ppcboot source
> code?
>
> Thanks,
> /************************/
> Rudolf Ladyzhenskii
> DSP Engineer
> Advanced Communication Technologies
> ph. +61 3 8080 8215
> fax. +61 3 9672 8800
> Level 9, 190 Queen Street,
> Melbourne, 3000
> Australia
> /***********************/
>
--
.....................................................................
Peter Desnoyers (781) 457-1165 pdesnoyers@chinook.com
Chinook Communications (617) 661-1979 pjd@fred.cambridge.ma.us
100 Hayden Ave, Lexington MA 02421
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-21 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 4:44 autoboot with initial RAM disk Rudolf Ladyzhenskii
2001-12-21 8:49 ` Wolfgang Denk
2001-12-21 16:01 ` Peter Desnoyers [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-21 5:17 Subodh Nijsure
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=3C235CE8.2E5E723C@chinook.com \
--to=pdesnoyers@chinook.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rudolf.ladyzhenskii@act-aus.net \
/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.