From: Eugene Surovegin <ebs@ebshome.net>
To: "Howard, Marc" <Marc.Howard@KLA-Tencor.com>
Cc: Linuxppc-embedded@ozlabs.org
Subject: Re: Gigibit ethernet ports on Ocotea + 2.6.10
Date: Thu, 24 Feb 2005 20:20:52 -0800 [thread overview]
Message-ID: <20050225042052.GA12703@gate.ebshome.net> (raw)
In-Reply-To: <91B22F93A880FA48879475E134D6F0BE8E7CB9@CA1EXCLV02.adcorp.kla-tencor.com>
On Thu, Feb 24, 2005 at 06:42:40PM -0800, Howard, Marc wrote:
> console=ttyS0,115200 root=/dev/nfs rw
> nfsroot=192.168.168.108:/projects/targets/ppc_4xx
> ip=192.168.168.111:192.168.168.108:192.168.168.108:255.255.255.0:ppc440:
> :off
You haven't searched archives very hard :).
Format of ip=... can be found in net/ipv4/ipconfig.c:
/*
* Decode any IP configuration options in the "ip=" or "nfsaddrs=" kernel
* command line parameter. It consists of option fields separated by colons in
* the following order:
*
* <client-ip>:<server-ip>:<gw-ip>:<netmask>:<host name>:<device>:<PROTO>
*
* Any of the fields can be empty which means to use a default value:
* <client-ip> - address given by BOOTP or RARP
* <server-ip> - address of host returning BOOTP or RARP packet
* <gw-ip> - none, or the address returned by BOOTP
* <netmask> - automatically determined from <client-ip>, or the
* one returned by BOOTP
* <host name> - <client-ip> in ASCII notation, or the name returned
* by BOOTP
* <device> - use all available devices
* <PROTO>:
* off|none - don't do autoconfig at all (DEFAULT)
* on|any - use any configured protocol
* dhcp|bootp|rarp - use only the specified protocol
* both - use both BOOTP and RARP (not DHCP)
*/
BTW, looks like your ip=.. line is incorrect, you missed <device>
parameter.
--
Eugene
prev parent reply other threads:[~2005-02-25 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 2:42 Gigibit ethernet ports on Ocotea + 2.6.10 Howard, Marc
2005-02-25 4:20 ` Eugene Surovegin [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=20050225042052.GA12703@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=Marc.Howard@KLA-Tencor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox