From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NetLoop initialization bug
Date: Tue, 31 Mar 2009 08:36:04 +0200 [thread overview]
Message-ID: <49D1B9D4.3000802@denx.de> (raw)
In-Reply-To: <660c0f820903300607v6f76575bsa8391e56c16f0d36@mail.gmail.com>
Hello Michael,
Michael Zaidman wrote:
> Please see my comments and updated patch below.
>
> On Mon, Mar 30, 2009 at 7:12 AM, Heiko Schocher <hs@denx.de> wrote:
>> Hello Michael,
>>
>> Michael Zaidman wrote:
[...]
>> The following 2 vars are just used, if CONFIG_CMD_CDP
>> is used, can we do a "#if defined" around it?
>>> + NetOurNativeVLAN = getenv_VLAN("nvlan");
>>> + NetOurVLAN = getenv_VLAN("vlan");
>
> These two variables have been initialized in original code for all
> protocols supported by u-boot. As I can see, at least the NetOurVLAN
> is used by most of them. This was the reason for keeping them in place.
Ok.
>> [...]
>>> @@ -443,18 +392,19 @@ restart:
>>> /* Start with a clean slate... */
>>> BootpTry = 0;
>>> NetOurIP = 0;
>>> - NetServerIP = getenv_IPaddr ("serverip");
>>> DhcpRequest(); /* Basically same as BOOTP */
>>> break;
>>> #endif
>>>
>>> case BOOTP:
>>> BootpTry = 0;
>>> + NetOurIP = 0;
>>>
>> why we need this here?
>
> Generally, for the same reason the DHCP does - "Start with a clean state..."
> On the other hand you are right - we do not need to clear the NetOurIP
> address for BOOTP, DHCP and RARP because the current implementation
> does not check it. So it has been removed in my new patch below.
thanks.
> Here is the updated patch:
>
> Subject: [U-Boot] [PATCH] NetLoop initialization bug
Hmm.. can you please add your commit message and your Signed-off-by
thanks
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-03-31 6:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 17:35 [U-Boot] [PATCH] NetLoop initialization bug Michael Zaidman
2009-03-27 7:59 ` Michael Zaidman
2009-03-30 5:12 ` Heiko Schocher
2009-03-30 7:45 ` Wolfgang Denk
2009-03-30 13:07 ` Michael Zaidman
2009-03-31 6:36 ` Heiko Schocher [this message]
2009-03-31 9:30 ` Detlev Zundel
2009-03-31 10:47 ` Michael Zaidman
2009-03-31 16:26 ` Michael Zaidman
2009-04-02 12:47 ` Detlev Zundel
2009-04-02 15:47 ` Michael Zaidman
2009-04-02 21:52 ` Ben Warren
2009-04-03 20:05 ` Wolfgang Denk
2009-04-03 20:20 ` Michael Zaidman
2009-04-03 20:28 ` Wolfgang Denk
2009-04-03 20:41 ` Ben Warren
2009-04-03 20:39 ` Ben Warren
2009-04-03 21:02 ` Michael Zaidman
-- strict thread matches above, loose matches on Subject: below --
2009-04-02 15:25 Michael Zaidman
2009-04-03 20:16 Michael Zaidman
2009-04-03 22:43 Michael Zaidman
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=49D1B9D4.3000802@denx.de \
--to=hs@denx.de \
--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