All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: wu zhangjin <wuzhangjin@gmail.com>
Cc: Waldemar Brodkorb <mail@waldemar-brodkorb.de>,
	Ralf Baechle <ralf@linux-mips.org>,
	"linux-mips" <linux-mips@linux-mips.org>
Subject: Re: zboot for brcm
Date: Thu, 17 Jun 2010 14:38:15 +0200	[thread overview]
Message-ID: <201006171438.15832.florian@openwrt.org> (raw)
In-Reply-To: <AANLkTikZc02RQ2zJ4Cj0nxUezYXyVIMxQS2opAWSjOrd@mail.gmail.com>

Hi,

On Thursday 17 June 2010 14:20:49 wu zhangjin wrote:
> Hi,
> 
> I just got a bcm1250a board, it also uses the CFE as the bootloader, I
> compiled a compressed vmlinuz-2.6.34 for it and boot with the
> following command, it works well:
> 
> CFE> setenv bootargs root=/dev/nfs rw
> nfsroot=$nfs_server_ip:/path/to/nfs_root_fs ip=dhcp
> CFE> ifconfig -auto eth0
> CFE> boot -elf $tftp_server_ip:/path/to/vmlinuz
> 
> With -elf, the boot command of CFE can parse the vmlinuz and boot it
> normally. I think you have used the wrong options of the boot command.

CFE on bcm12xx, on bcm47xx and bcm63xx are all three slightly different flavors 
which may not behave exactly the same way wrt the load command.

Also, you are on a development board so there are no reasons to restrict CFE 
commands, this is not the case with end-user products like WRT54G and such.
--
Florian

  reply	other threads:[~2010-06-17 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100609153831.GA27461@waldemar-brodkorb.de>
     [not found] ` <1276099374.4510.13.camel@localhost>
     [not found]   ` <20100609172438.GA23116@waldemar-brodkorb.de>
2010-06-10 14:14     ` zboot for brcm Wu Zhangjin
2010-06-17 12:20       ` wu zhangjin
2010-06-17 12:38         ` Florian Fainelli [this message]
2010-06-17 13:31           ` Wu Zhangjin
2010-09-12 17:13             ` Florian Fainelli
2010-09-15 13:28               ` Ralf Baechle

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=201006171438.15832.florian@openwrt.org \
    --to=florian@openwrt.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mail@waldemar-brodkorb.de \
    --cc=ralf@linux-mips.org \
    --cc=wuzhangjin@gmail.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 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.