From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] x86: Fix regression build issue of coreboot-x86_defconfig
Date: Thu, 28 May 2015 16:22:23 +0100 [thread overview]
Message-ID: <01b301d0995a$1f3c3450$5db49cf0$@pont@sdcsystems.com> (raw)
In-Reply-To: <CAEUhbmUqJuy1i=Yqbex2_UvuakcZtryfe3G5ThrX1K0qLfx_Yg@mail.gmail.com>
Hi Bin,
> I just found u-boot.rom created from u-boot-x86/testing branch does
> not have working network any more on QEMU. It is working on the
> u-boot-x86/master branch.
>
> => set serverip 10.10.0.100;set ipaddr 10.10.0.108;set netmask
> 255.255.255.0;set gatewayip 10.10.0.100
> => run ramboot
> *** ERROR: `serverip' not set
> *** ERROR: `serverip' not set
>
> But 'print' says the env indeed has the 'serverip'. I think there
> should be something in the upstream that caused this after the
> u-boot-x86/testing branch rebase. Do you know where might be the
> problem?
This looks very similar to an issue that got patched on the i.MX6 yesterday
by Stefano which said:
commit fd3056337e6fcc140f400e11edd33f6f1cb37de1
"Use env callbacks for net variables" has a side effect on i.MX6 boards
because they do not set CONFIG_NET: the ip address results not set, but it
is stored in the environment."
Might be something to check...
Regards,
Andy.
next prev parent reply other threads:[~2015-05-28 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 15:55 [U-Boot] [PATCH] x86: Fix regression build issue of coreboot-x86_defconfig Bin Meng
2015-05-27 16:01 ` Bin Meng
2015-05-27 16:13 ` Joe Hershberger
2015-05-27 16:21 ` Bin Meng
2015-05-27 16:27 ` Joe Hershberger
2015-05-27 23:25 ` Simon Glass
2015-05-27 23:51 ` Joe Hershberger
2015-05-28 3:04 ` Bin Meng
2015-05-28 2:41 ` Bin Meng
2015-05-28 2:55 ` Simon Glass
2015-05-28 3:10 ` Bin Meng
2015-05-28 15:05 ` Bin Meng
2015-05-28 15:22 ` Andy Pont [this message]
2015-05-28 23:24 ` Simon Glass
2015-05-29 7:23 ` Bin Meng
[not found] ` <556732bd.0e4d320a.3628.ffffc5eeSMTPIN_ADDED_BROKEN@mx.google.com>
2015-05-29 3:03 ` Bin Meng
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='01b301d0995a$1f3c3450$5db49cf0$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.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