From: "El Topo" <ElTopo@myrealbox.com>
To: <erik.teose@exgate.tek.com>, <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ppcboot 2.0.0 + ppclinux2.4.devel, network weirdo
Date: Wed, 9 Apr 2003 11:33:54 -0700 [thread overview]
Message-ID: <001f01c2fec6$94091c80$1464a8c0@sjeng3> (raw)
In-Reply-To: BA0E4392AD99D040885C414D992C24BE03615100@us-bv-m11
> Are you using kernel code supplied by MontaVista (MV)? I had the same
> problem;
> we are using MontaVista 3.0 for the Ebony board, and I had trouble with
> the interface from u-boot 0.2.0 to the MV kernel. The MV code is very
> specific to the bootrom supplied by IBM; that bootrom is "custom" to each
> unique Ebony board, because the 2 MAC addresses are stored at the end of
the
> bootrom (that's the "VPD" area). I had to modify 3 MV files to get the MAC
> address passed in from u-boot to be used by the MV kernel
> (kernel/arch/ppc/platforms/ebony.c,
> kernel/include/asm-ppc/ibm440.h, and kernel/include/asm-ppc/ibm4xx.h). I
> have attached
> my patches for these files.
>
> After I got the MAC address to transfer over from u-boot, I had trouble
with
> nfs mounting
> the root filesystem (I did not want to use bootp/dhcp in the nfs mounting
> process). I had to
> modify kernel/net/ipv4/ipconfig.c to get this to work (I've attached this
> patch as well).
>
> Hope this helps.
>
> Erik Teose
> erik.teose@tek.com
Thank you Erik, I will try your patchs today.
El.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-09 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 16:23 ppcboot 2.0.0 + ppclinux2.4.devel, network weirdo erik.teose
2003-04-09 18:33 ` El Topo [this message]
2003-04-09 21:14 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
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
2003-04-09 18:32 ` El Topo
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='001f01c2fec6$94091c80$1464a8c0@sjeng3' \
--to=eltopo@myrealbox.com \
--cc=erik.teose@exgate.tek.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).