From: Wolfgang Denk <wd@denx.de>
To: "El Topo" <ElTopo@myrealbox.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppcboot 2.0.0 + ppclinux2.4.devel, network weirdo
Date: Wed, 09 Apr 2003 11:37:12 +0200 [thread overview]
Message-ID: <20030409093717.B115AC5877@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 09 Apr 2003 01:46:27 PDT." <000d01c2fe74$83264520$1464a8c0@sjeng3>
In message <000d01c2fe74$83264520$1464a8c0@sjeng3> you wrote:
>
> Here's my 2nd question: is it a good idea that I modify ppcboot to
> include these network initialization functions just before booting my
> kernel image? Maybe this is not necessary but I really could not figure
> out why the "tftp" before loading kernel image made the difference
> on the network.
This is a somewhat philosophical question, and opinions differ. IMHO
a Linux driver usually should perform all required initializations
himself instead on relying on certain things to be done by some
firmware.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"...one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C programs." - Robert Firth
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-09 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 15:58 Linux kernel panics and core dumps Arun Dharankar
2003-04-09 8:46 ` ppcboot 2.0.0 + ppclinux2.4.devel, network weirdo El Topo
2003-04-09 9:37 ` Wolfgang Denk [this message]
2003-04-09 18:32 ` El Topo
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 16:23 erik.teose
2003-04-09 18:33 ` El Topo
2003-04-09 21:14 ` 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=20030409093717.B115AC5877@atlas.denx.de \
--to=wd@denx.de \
--cc=ElTopo@myrealbox.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).