From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC][PATCH 1/1] Add board_eth_init() function
Date: Wed, 26 Mar 2008 12:43:50 +0100 [thread overview]
Message-ID: <200803261243.51429.sr@denx.de> (raw)
In-Reply-To: <20080326120610.71996505@hskinnemo-gx620.norway.atmel.com>
On Wednesday 26 March 2008, Haavard Skinnemoen wrote:
> > Yes, same SoC ethernet interfaces. Currently PHY address etc is
> > configured via config options.
>
> Judging by the number of #ifdefs in ppc_4xx_eth_initialize, that
> function contains quite a bit of board-specific code.
Most of it is not board-specific, but platform-specific. This driver handles
all 4xx EMAC variants and there are quite a lot. But basically you are
correct.
> > > Can't you just add a weak definition of board_eth_init() in the CPU
> > > code then?
> >
> > No. The weak definition is already in net/eth.c.
>
> Make it non-weak then.
In net/eth.c? It can't get overwritten then.
> If a platform wants to implement board-specific
> ethernet init code as #ifdef hell, it should be free to do so. I don't
> think we should add workarounds in the generic code for such platforms
> though.
I could use board_eth_init() as a common PPC4xx platform code. But I would
loose the chance being able to implement a "real" board specific
board_eth_init() for some boards in the future then.
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:[~2008-03-26 11:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 2:46 [U-Boot-Users] [RFC][PATCH 1/1] Add board_eth_init() function Ben Warren
2008-03-22 5:03 ` Shinya Kuribayashi
[not found] ` <f8328f7c0803220505n39c9ddb5sf9c9cf037b8f4665@mail.gmail.com>
2008-03-22 12:07 ` Ben Warren
2008-03-22 15:55 ` Vlad Lungu
2008-03-23 6:19 ` Shinya Kuribayashi
2008-03-26 10:00 ` Haavard Skinnemoen
2008-03-26 11:39 ` Shinya Kuribayashi
2008-03-26 12:41 ` Haavard Skinnemoen
2008-03-26 14:15 ` Ben Warren
2008-03-26 14:27 ` Haavard Skinnemoen
2008-03-22 6:31 ` Stefan Roese
2008-03-22 9:59 ` Wolfgang Denk
2008-03-22 10:14 ` Stefan Roese
2008-03-22 11:35 ` Markus Klotzbücher
2008-03-22 14:01 ` Wolfgang Denk
2008-03-22 15:43 ` Ben Warren
2008-03-25 7:04 ` Stefan Roese
2008-03-25 11:11 ` Ben Warren
2008-03-25 14:22 ` Ben Warren
2008-03-25 14:41 ` Joakim Tjernlund
2008-03-25 14:57 ` Ben Warren
2008-03-25 15:31 ` Joakim Tjernlund
2008-03-25 15:56 ` Jerry Van Baren
2008-03-25 16:59 ` Joakim Tjernlund
2008-03-25 14:43 ` Stefan Roese
2008-03-25 16:17 ` Andy Fleming
2008-03-25 16:33 ` Stefan Roese
2008-03-25 17:04 ` Andy Fleming
2008-03-25 17:53 ` Ben Warren
2008-03-26 10:06 ` Haavard Skinnemoen
2008-03-26 10:14 ` Stefan Roese
2008-03-26 10:25 ` Haavard Skinnemoen
2008-03-26 10:34 ` Stefan Roese
2008-03-26 11:06 ` Haavard Skinnemoen
2008-03-26 11:43 ` Stefan Roese [this message]
2008-03-26 12:19 ` Haavard Skinnemoen
2008-03-26 12:39 ` Stefan Roese
2008-03-23 0:06 ` [U-Boot-Users] [OT] Using MTD to manipulate CFI flash on PCI boards? David Hawkins
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=200803261243.51429.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox