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] Environmentvar. "ipaddr" - microblaze
Date: Tue, 23 Mar 2010 14:41:27 +0100	[thread overview]
Message-ID: <4BA8C507.9030501@monstr.eu> (raw)
In-Reply-To: <008b01caca78$85c2c1a0$c801a8c0@xeon>

Horst Gall wrote:
>> Horst: Give me step-by-step manual how to reach that fault.
> 
> Hi Michal,
> 
> in 'include/configs/microblaze_generic.h' is ipaddr defined:
>    #define CONFIG_IPADDR 192.168.0.3
> 
> Now run uboot:
> 
>    setenv ipaddr 192.168.0.1
>    saveenv
> 
> Reboot the board
> 
>    printenv (tells ipaddr 192.168.0.1)
>    bdinfo    (tells ipaddr 192.168.0.3)
> 
>    tftpboot also use ipaddr 192.168.0.3
> 
> 
> On a ppc-based board bdinfo tells 192.168.0.1
> 
> So I found the difference in the order of the two functions in 
> lib_microblaze/board.c board_init():
> 
>    env_relocate()                (ppc-order witch works)
>    getenv_IPaddr()
> 
> instead of:
> 
>    getenv_IPaddr()            (microblaze-order)
>    env_relocate()

I got it. Dentlev described what is going on.
Please create proper patch and send it to mailing list with cc to me.

Thanks,
Michal

> 
> 
> Best regards
> Horst
> 


-- 
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:[~2010-03-23 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 22:12 [U-Boot] Environmentvar. "ipaddr" - microblaze Horst Gall
2010-03-18  9:38 ` Detlev Zundel
2010-03-22 13:20   ` Michal Simek
2010-03-22 16:40     ` Detlev Zundel
2010-03-22 17:24       ` Michal Simek
2010-03-23  9:55         ` Detlev Zundel
2010-03-23 13:44           ` Michal Simek
2010-03-23 11:03     ` Horst Gall
2010-03-23 13:41       ` 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=4BA8C507.9030501@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