All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Seiler <hws@denx.de>
To: Valerio Nappi <valerio.nappi@cern.ch>, u-boot@lists.denx.de
Cc: Joe Hershberger <joe.hershberger@ni.com>
Subject: Re: TFTP boot using DNS
Date: Thu, 15 Dec 2022 13:55:09 +0100	[thread overview]
Message-ID: <487d2f2dce8bfc449f0cdad42454353ced8ae514.camel@denx.de> (raw)
In-Reply-To: <0acd0f92-066e-210e-c45f-b25b5f07bd50@cern.ch>

Hi Valerio,

On Thu, 2022-12-15 at 10:27 +0100, Valerio Nappi wrote:
> Hello everyone,
> 
> Context:
> I'm new to the u-boot project. I am trying to boot a Zynq SoC from an
> internal TFTP server, but i have no guarantee that the IP of the
> server is going to stay the same. A DNS service is offered, and kept
> updated.
> 
> When i try to update the serverip variable using the dns <myserver>
> serverip command, the variable seems updated (in the sense that I can
> print the new value) but it is not. Apparently this is ignored on
> purpose at this line of the source [1]. Commit fd3056337 that
> introduced this change, mentions "Don't update the variables when the
> source was programmatic, since the variables were the source of the
> new value.", that is not true in this case, in fact the source of the
> new value is the DNS service.
> 
> Is there a particular reason why this usecase was not forseen?

Unrelated to your point about proper support for this usecase, but maybe
you can use the following as a workaround in the meantime?

	tftp ${loadaddr} ${serverip}:path/to/file

Also adding Joe on CC as he authored the commit you mentioned.

-- 
Harald

  reply	other threads:[~2022-12-15 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  9:27 TFTP boot using DNS Valerio Nappi
2022-12-15 12:55 ` Harald Seiler [this message]
2022-12-15 14:42   ` Valerio Nappi

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=487d2f2dce8bfc449f0cdad42454353ced8ae514.camel@denx.de \
    --to=hws@denx.de \
    --cc=joe.hershberger@ni.com \
    --cc=u-boot@lists.denx.de \
    --cc=valerio.nappi@cern.ch \
    /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.