From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Add mechanisms for CPU and board-specific Ethernet initialization
Date: Tue, 10 Jun 2008 17:25:37 +0200 [thread overview]
Message-ID: <200806101725.37247.sr@denx.de> (raw)
In-Reply-To: <484E9AD9.2060802@ruby.dti.ne.jp>
On Tuesday 10 June 2008, Shinya Kuribayashi wrote:
> >> Shouldn't this be the other way around?
> >>
> >> + if (board_eth_init(bis) < 0)
> >> + eth_eth_init(bis);
> >>
> >> So that the board init routine can "overwrite" the cpu init version.
> >
> > Yeah, I think you're right. If board_eth_init() exists, it gets
> > highest priority.
>
> Just wondered, does that mean we could only have either cpu_eth_init or
> board_eth_init at a time?
Not really. board_eth_init() could call cpu_eth_init() if necessary.
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-06-10 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 8:29 [U-Boot-Users] [PATCH] Add mechanisms for CPU and board-specific Ethernet initialization Ben Warren
2008-06-10 9:12 ` Stefan Roese
2008-06-10 13:53 ` Ben Warren
2008-06-10 15:16 ` Shinya Kuribayashi
2008-06-10 15:25 ` Stefan Roese [this message]
2008-06-10 15:49 ` Shinya Kuribayashi
2008-06-10 16:16 ` Ben Warren
2008-06-24 22:32 ` Jean-Christophe PLAGNIOL-VILLARD
2008-06-24 23:05 ` Ben Warren
2008-06-25 9:30 ` Haavard Skinnemoen
2008-06-25 9:34 ` Stefan Roese
2008-06-11 0:50 ` Haavard Skinnemoen
2008-06-11 11:30 ` Jerry Van Baren
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=200806101725.37247.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