From: T Ziomek <Tom.Ziomek@motorola.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Support for sending DHCP client options
Date: Tue, 19 Oct 2010 14:02:45 -0500 [thread overview]
Message-ID: <20101019190245.GA7751@email.mot.com> (raw)
In-Reply-To: <4CBDA038.7020209@rocketmail.com>
On Tue, Oct 19, 2010 at 02:42:16PM +0100, Gray Remlin wrote:
> Signed-off-by: Gray Remlin <g_remlin@rocketmail.com>
> ---
> README | 7 ++++++
> common/cmd_nvedit.c | 3 ++
> net/bootp.c | 52
> +++++++++++++++++++++++++++++++++++++++++++++++++++
> tools/env/fw_env.c | 4 ++-
> 4 files changed, 65 insertions(+), 1 deletions(-)
>
> diff --git a/README b/README
> index a52f3bf..90da375 100644
> --- a/README
> +++ b/README
> @@ -1279,6 +1279,7 @@ The following options need to be configured:
> CONFIG_BOOTP_NTPSERVER
> CONFIG_BOOTP_TIMEOFFSET
> CONFIG_BOOTP_VENDOREX
> + CONFIG_BOOTP_OPTIONS
>
> CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
> environment variable, not the BOOTP server.
> @@ -1299,6 +1300,12 @@ The following options need to be configured:
> of the "hostname" environment variable is passed as
> option 12 to the DHCP server.
>
> + CONFIG_BOOTP_OPTIONS - The environment is checked for the
> + supported DHCPv4 client options (prefixed with dhcp_), any
> + found are sent during a "DHCP Discover" and "DHCP Request".
> + The DHCP server can use this information to conditionally
> + tailor it's response.
s/it's/its/
--
It is of fundamental importance to understand |
that the primary recipient of your source code | Email to 'CTZ001'
is not the compiler but your coworkers. | at 'email.mot.com'
-- KreaTV SW Dev Guidelines |
prev parent reply other threads:[~2010-10-19 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 13:42 [U-Boot] [PATCH] Support for sending DHCP client options Gray Remlin
2010-10-19 19:02 ` T Ziomek [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=20101019190245.GA7751@email.mot.com \
--to=tom.ziomek@motorola.com \
--cc=u-boot@lists.denx.de \
/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.