From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/next branch] powerpc: Only use eth_getenv_enetaddr() if networking is enabled
Date: Wed, 25 Feb 2009 10:29:42 +0100 [thread overview]
Message-ID: <200902251029.42273.sr@denx.de> (raw)
In-Reply-To: <20090225091653.EB79E832E43F@gemini.denx.de>
On Wednesday 25 February 2009, Wolfgang Denk wrote:
> > +++ b/lib_ppc/board.c
> > @@ -888,8 +888,10 @@ void board_init_r (gd_t *id, ulong dest_addr)
> > bd->bi_ethspeed = 0xFFFF;
> > #endif
> >
> > +#ifdef CONFIG_CMD_NET
> > /* kept around for legacy kernels only ... ignore the next section */
> > eth_getenv_enetaddr("ethaddr", bd->bi_enetaddr);
> > +#endif
> > #ifdef CONFIG_HAS_ETH1
> > eth_getenv_enetaddr("eth1addr", bd->bi_enet1addr);
> > #endif
>
> Should that #ifdef not include the code for "eth1addr" etc., too?
I don't think this is needed. If a board has a 2nd (or 3rd...) ethernet
interface, it sets CONFIG_HAS_ETH1. I can't think of a board setting this
define and not enabling CONFIG_CMD_NET.
But if you prefer it, I could change the patch to include all eth interfaces
in the #ifdef CONFIG_CMD_NET part. Just let me know.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-02-25 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 15:52 [U-Boot] [PATCH/next branch] powerpc: Only use eth_getenv_enetaddr() if networking is enabled Stefan Roese
2009-02-25 9:16 ` Wolfgang Denk
2009-02-25 9:29 ` Stefan Roese [this message]
2009-02-25 10:54 ` Wolfgang Denk
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=200902251029.42273.sr@denx.de \
--to=sr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.