public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Duncan Hare <dh@synoia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fw: dhcp command not populating dnsip environment variable
Date: Mon, 19 Mar 2018 15:03:22 -0700	[thread overview]
Message-ID: <20180319150322.33fa7d1c@raspberrypi> (raw)



Begin forwarded message:

Date: Mon, 19 Mar 2018 14:57:59 -0700
From: Duncan Hare <dh@synoia.com>
To: Duncan Hare <dh@synoia.com>
Subject: Re: [U-Boot] dhcp command not populating dnsip environment
variable

> >On Sun, Mar 18, 2018 at 3:01 PM, Duncan Hare <dh@synoia.com> wrote:  
> > Cause: u-boot/Kconfig DISTRO_DEFAULTS missing variables in Kconfig
> > files
> >
> >        BOOTP_BOOTPATH
> >        BOOTP_DNS
> >        BOOTP_GATEWAY
> >        BOOTP_HOSTNAME
> >        BOOTP_SUBNETMASK
> > 	   BOOTP_PXE  
	

> It seems like we should imply them. That means we always get good
> defaults but can still disable them if desired.  

All of the above defined in net/KConfig? 



net/Kconfig adds

config BOOTP_BOOTPATH
config BOOTP_DNS
config BOOTP_GATEWAY
config BOOTP_HOSTNAME
config BOOTP_SUBNETMASK
config BOOTP_PXE

and in the distro_defaults change the select verb to imply? Or
imply them all under the cmd/net.c BOOTP command?

                 reply	other threads:[~2018-03-19 22:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180319150322.33fa7d1c@raspberrypi \
    --to=dh@synoia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox