From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] imx: missing CONFIG_NET after consolidation patches
Date: Fri, 29 May 2015 07:19:31 +0200 [thread overview]
Message-ID: <5567F6E3.90502@denx.de> (raw)
In-Reply-To: <CAEUhbmU2UjkqNqBEqRSZZhbOKjvr5V-RW+by3fsLhgSovy0e4w@mail.gmail.com>
Hello Bin,
Am 29.05.2015 04:33, schrieb Bin Meng:
> Hi Joe,
>
> On Fri, May 29, 2015 at 1:53 AM, Joe Hershberger
> <joe.hershberger@gmail.com> wrote:
>> Hi Stefano,
>>
>> On Wed, May 27, 2015 at 4:29 AM, Stefano Babic <sbabic@denx.de> wrote:
>>> 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.
>>>
>>> => pri ipaddr
>>> ipaddr=192.168.178.66
>>> => ping 192.168.178.1
>>> *** ERROR: `ipaddr' not set
>>> ping failed; host 192.168.178.1 is not alive
>>>
>>> Setting CONFIG_NET solves this issue.
>>>
>>> Reported-by: Heiko Schoker <hs@denx.de>
>>> Signed-off-by: Stefano Babic <sbabic@denx.de>
>>> ---
>>> include/configs/mx6_common.h | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/include/configs/mx6_common.h b/include/configs/mx6_common.h
>>> index 233c6d2..3d859cf 100644
>>> --- a/include/configs/mx6_common.h
>>> +++ b/include/configs/mx6_common.h
>>> @@ -105,4 +105,7 @@
>>> #define CONFIG_FSL_ESDHC
>>> #define CONFIG_FSL_USDHC
>>>
>>> +/* NET */
>>> +#define CONFIG_NET
>>
>> This config was added to Kconfig here:
>>
>> 60296a8 commands: add more command entries in Kconfig
>
> Looks CONFIG_NET was added by commit ed36323
>
> commit ed36323f6d217050f82a2200475959b8557a47e4
> Author: Masahiro Yamada <yamada.m@jp.panasonic.com>
> Date: Tue Sep 16 16:32:58 2014 +0900
>
> kconfig: add blank Kconfig files
>
>> Author: Masahiro Yamada <yamada.m@jp.panasonic.com>
>> Date: Thu Nov 13 19:29:08 2014 +0900
>>
>> Apparently some of the boards that supported NET previously were not
>> properly added to their defconfigs.
>>
>> In any case, for this board, you should add the NET config to the
>> defconfig, not the header.
>>
>>> #endif
>>
>
> But I failed to understand why adding CONFIG_NET could resolve the
> "*** ERROR: `ipaddr" not set' problem. A grep of "^CONFIG_NET" gives
> me nothing helpful.
Reason is the following commit:
commit fd3056337e6fcc140f400e11edd33f6f1cb37de1
Author: Joe Hershberger <joe.hershberger@ni.com>
Date: Wed May 20 14:27:23 2015 -0500
net: Use env callbacks for net variables
if CONFIG_NET is not defined, NET_CALLBACKS is empty, which results
in the above error message ...
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2015-05-29 5:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 9:29 [U-Boot] [PATCH] imx: missing CONFIG_NET after consolidation patches Stefano Babic
2015-05-28 5:28 ` Heiko Schocher
2015-05-28 17:53 ` Joe Hershberger
2015-05-29 2:33 ` Bin Meng
2015-05-29 5:19 ` Heiko Schocher [this message]
2015-05-29 7:16 ` Bin Meng
2015-05-29 7:43 ` Joe Hershberger
2015-06-01 17:14 ` Simon Glass
2015-06-01 17:17 ` Joe Hershberger
2015-06-02 0:41 ` Bin Meng
2015-05-29 5:28 ` Heiko Schocher
2015-05-29 6:09 ` Joe Hershberger
2015-05-29 6:15 ` Heiko Schocher
2015-05-29 7:31 ` Stefano Babic
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=5567F6E3.90502@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