From: Jeff H Zhong <jeff@doremilabs.com>
To: Wolfgang Denk <wd@denx.de>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: debugging using bdi2000, unable to proceed.
Date: Fri, 18 Apr 2003 10:49:51 +0000 [thread overview]
Message-ID: <3E9FD84F.2C40F0ED@doremilabs.com> (raw)
In-Reply-To: 20030418160238.8EB5BC58B9@atlas.denx.de
The problem is this:
When I use bootp/tftp boot, on the host if I do arp then I can get
root@Jeff linuxppc_2_4_develubpatch<366>arp
Address HWtype HWaddress Flags
Mask Iface
7.1.1.5 ether 00:40:49:FA:43:59
C eth1
7.1.1.6 ether 00:04:AC:E3:1D:62
C eth1
10.1.1.171 ether 00:A0:C5:E0:C4:EC
C eth0
Which 7.1.1.5 is my BDI2000 and is not part of our discussion.
But if I bootm directly from flash, it will be
root@Jeff linuxppc_2_4_develubpatch<366>arp
Address HWtype HWaddress Flags
Mask Iface
7.1.1.5 ether 00:40:49:FA:43:59
C eth1
7.1.1.6
(incomplete) eth1
10.1.1.171 ether 00:A0:C5:E0:C4:EC
C eth0
I doubt that when kernel brings up eth0, it doesn't broadcast MAC
address?
I am still hacking the kernel code.... and getting headache on this
problem...
--Jeff
Wolfgang Denk wrote:
>
> in message <3E9FB7FD.93947BE5@doremilabs.com> you wrote:
> >
> > Could you give me a hand to help me figure out this issue on ebony?
>
> I've read your story before, but I cannot help.
>
> > If I use "bootp" or "tftp" to load kernel image(linuxppc_2_4_devel from
> > BK) at address 0x01000000 and then issue "bootm", everything works fine.
> > I have also programmed the image into flash at 0xffe00000, but each time
> > when I issue "bootm 0xffe00000", it will get stuck at when trying to
> > mount NFS.
>
> Technically there is absolutely no difference between both cases: in
> either case U-Boot will copy and uncompress the kernel to RAM
> starting at physical adress 0x0000, and start it there. I have not
> the slightest idea whaty could cause a behaviour as described by you,
> nor have I ever seen anything like that before.
--
Jeff H. Zhong
-------------
Doremi Labs, Inc.
306 East Alameda Avenue
Burbank, CA 91502
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-04-18 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030418160238.8EB5BC58B9@atlas.denx.de>
2003-04-18 10:49 ` Jeff H Zhong [this message]
2003-04-18 22:22 ` debugging using bdi2000, unable to proceed Wolfgang Denk
2003-04-18 15:59 ` Jeff H Zhong
2003-04-18 23:23 ` Wolfgang Denk
2003-04-18 16:12 ` Jeff H Zhong
2003-04-18 23:24 ` Wolfgang Denk
2003-04-17 13:10 Omanakuttan
2003-04-17 13:45 ` Wolfgang Denk
2003-04-18 11:43 ` Omanakuttan
2003-04-18 14:51 ` 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=3E9FD84F.2C40F0ED@doremilabs.com \
--to=jeff@doremilabs.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.