public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] bootp: Fix bug in auto_load function
Date: Thu, 01 Sep 2011 07:39:57 +0200	[thread overview]
Message-ID: <4E5F1AAD.9010500@monstr.eu> (raw)
In-Reply-To: <20110831200152.1901918D30CE@gemini.denx.de>

Hi,

Wolfgang Denk wrote:
> Dear Michal Simek,
> 
> In message <1314786967-23261-1-git-send-email-monstr@monstr.eu> you wrote:
>> Patch: "Put common autoload code into auto_load() function"
>> (sha1: 093498669e77597635a24f326f11efeab213d394) is not simple code
>> cleanup but code change which introduce new bug.
>>
>> If autoload variable is not setup it worked as autoload=yes.
> 
> Yes, and this is intentionally, because it's what poople expect when
> they run the "dhcpboot" command.

ok.

> 
>> Currently if autoload is not setup dhcp sends request in
>> forever loop.
> 
> That's not correct.  Only until a DHCP server provides the needed
> configurationinformation so TFTP gets started.

That's what I get/see on my platforms.

> 
>> There are two options how to fix it:
>> 1. Move TftpStart() which is in this patch
>> 2. Change functionality if autoload is not setup, set NetSate and ends.
> 
> That would change behavious in a way that is not wanted.

Agree that point 2 change behavior.
Point 1 just fix c&p error.

Regards,
Michal


-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

      reply	other threads:[~2011-09-01  5:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 10:36 [U-Boot] [PATCH] bootp: Fix bug in auto_load function Michal Simek
2011-08-31 16:31 ` Simon Glass
2011-08-31 19:11   ` Michal Simek
2011-08-31 20:01 ` Wolfgang Denk
2011-09-01  5:39   ` Michal Simek [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=4E5F1AAD.9010500@monstr.eu \
    --to=monstr@monstr.eu \
    --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