From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] ARM: add support of CONFIG_LAST_STAGE_INIT for arm
Date: Mon, 10 Dec 2007 21:08:28 +0100 [thread overview]
Message-ID: <475D9CBC.2080005@discworld.dascon.de> (raw)
In-Reply-To: <20071210185827.4f3c005b@dhcp-252-066.norway.atmel.com>
Haavard Skinnemoen wrote:
> Or even better, move eth_initialize into the board code. That would
> allow us to kill a ridiculous number of #ifdefs in net/eth.c and would
> allow the board to do any fixups it needs before and after the generic
> code.
>
Hm - yes, looking at eth_initialize, that does sound like a good idea,
although some common init code and the code handling ethact / ethprime
(what is that good for, anyway?) would need to be factored out.
cu
Michael
next prev parent reply other threads:[~2007-12-10 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 15:29 [U-Boot-Users] PATCH: support board-specific ethernet PHY init for ARM Michael Schwingen
2007-12-08 12:45 ` Jean-Christophe PLAGNIOL-VILLARD
2007-12-08 22:32 ` Michael Schwingen
2007-12-09 9:43 ` Jean-Christophe PLAGNIOL-VILLARD
2007-12-09 9:50 ` [U-Boot-Users] [PATCH] ARM: add support of CONFIG_LAST_STAGE_INIT for arm Jean-Christophe PLAGNIOL-VILLARD
2007-12-09 14:50 ` Wolfgang Denk
2007-12-09 16:38 ` Michael Schwingen
2007-12-10 17:58 ` Haavard Skinnemoen
2007-12-10 20:08 ` Michael Schwingen [this message]
2007-12-10 20:28 ` Ben Warren
2007-12-11 8:59 ` Haavard Skinnemoen
2007-12-11 16:13 ` Wolfgang Denk
2007-12-11 17:05 ` Mike Frysinger
2007-12-11 22:03 ` Wolfgang Denk
2007-12-11 18:38 ` Michael Schwingen
2007-12-11 22:09 ` Wolfgang Denk
2007-12-12 8:32 ` Michael Schwingen
2007-12-11 9:53 ` [U-Boot-Users] [PATCH] ARM: support board-specific ethernet PHY init Jean-Christophe PLAGNIOL-VILLARD
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=475D9CBC.2080005@discworld.dascon.de \
--to=rincewind@discworld.dascon.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