From: Wolfgang Denk <wd@denx.de>
To: hjzgq@sohu.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Change FEC and SCC1 sequence,But SCC1 not work?
Date: Thu, 10 Jun 2004 19:17:56 +0200 [thread overview]
Message-ID: <20040610171801.09859C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 10 Jun 2004 17:12:34 +0800." <5357004.1086858754080.JavaMail.postfix@mx27.mail.sohu.com>
In message <5357004.1086858754080.JavaMail.postfix@mx27.mail.sohu.com> you wrote:
>
> Briefly, my platform is MPC860T from Motorola. I'm using ppcboot 1.1.16
> to tftp the kernel 2.4.4 through FEC and then load NFS/RAMDISK. If I
> configure the kernel with only FEC, then everything works well(NFS
> works and ping through eth0 works). If I configure the kernel with both
> FEC(as eth0) and SCC1(as eth1),it works well too,but when I configure
> ther kernel with both SCC1(eth0) and FEC(as eth1) (net/setup.c)! . I
> try to ping out through FEC(eth1), I get ring buffer dumps and no ping
> response:
Please post the "Kernel command line" as printed when your kernel
boots. You did include a network device parameter in your ip= boot
argument, didn't you?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
My challenge to the goto-less programmer is to recode tcp_input()
without any gotos ... without any loss of efficiency (there has to be
a catch). - W. R. Stevens
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-10 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 9:12 Change FEC and SCC1 sequence,But SCC1 not work? hjzgq
2004-06-10 16:52 ` Mark Chambers
2004-06-10 17:17 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 6:22 hjzgq
2004-06-11 16:02 ` 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=20040610171801.09859C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=hjzgq@sohu.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).