From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Mark E Mason <mason@broadcom.com>
Cc: LMO <linux-mips@linux-mips.org>,
"mmason@upwardaccess.com" <mmason@upwardaccess.com>
Subject: RE: Booting top-of-tree bcm47xx as nfs-root with cfe only (no sibyl)
Date: Wed, 26 Nov 2008 23:52:06 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0811262340550.23566@ftp.linux-mips.org> (raw)
In-Reply-To: <BD3F7F1EFBA6D54DB056C4FFA45140080348EC8037@SJEXCHCCR01.corp.ad.broadcom.com>
On Wed, 26 Nov 2008, Mark E Mason wrote:
> Do you mean something like this?
>
> setenv LINUX_CMDLINE "root=/dev/nfs rw ip=dhcp nfsroot=10.0.1.184:/home/mason/debian-root-el"
Yes, it should work.
> What about CONIFG_ROOT_NFS? Some of the HOWTOs on the net mention it,
> and it's still in some (most) of the default config files except for the
> bcm47xx (but I added it to mine manually as I couldn't find it in the
> menuconfig). So it shouldn't matter... Except that I'm paraniod... Is
> this a left over 2.4-ism?
For your configuration you need at least these:
CONFIG_NET=y
CONFIG_INET=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_ROOT_NFS=y
In the absence of a platform maintainer the respective default config
files are at the very best only updated so that `make oldconfig' does not
ask questions.
Maciej
prev parent reply other threads:[~2008-11-26 23:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 22:56 Booting top-of-tree bcm47xx as nfs-root with cfe only (no sibyl) Mark E Mason
2008-11-26 23:10 ` Maciej W. Rozycki
2008-11-26 23:21 ` Mark E Mason
2008-11-26 23:31 ` Andrew Sharp
2008-11-26 23:57 ` Mark E Mason
2008-11-27 11:09 ` Maciej W. Rozycki
2008-11-27 16:20 ` David Pelton
2008-11-27 16:20 ` David Pelton
2008-11-26 23:52 ` Maciej W. Rozycki [this message]
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=alpine.LFD.1.10.0811262340550.23566@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mason@broadcom.com \
--cc=mmason@upwardaccess.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.