From: Wolfgang Denk <wd@denx.de>
To: "zhongqx" <zhongqx@guoguang.com.cn>
Cc: "Dave Ellis" <DGE@sixnetio.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Why FEC and SCC1 can not work at the same time?
Date: Wed, 18 Sep 2002 18:40:05 +0200 [thread overview]
Message-ID: <20020918164010.D32BAFA8D@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 18 Sep 2002 13:42:00 +0800." <001801c25ed6$1c389e00$7301a8c0@zhongqx>
In message <001801c25ed6$1c389e00$7301a8c0@zhongqx> you wrote:
>
> thank you very much,
> what you said is very right,fix ppcboot just like you said,and the proplem disappear!
Oops??? Dave did not mention any changes to PPCBoot, it seems.
PPCBoot is not to blame for your trouble.
> ----- Original Message -----
> From: "Dave Ellis" <DGE@sixnetio.com>
> To: "'zhongqx'" <zhongqx@guoguang.com.cn>
> Cc: <linuxppc-embedded@lists.linuxppc.org>
> Sent: Wednesday, September 18, 2002 4:20 AM
> Subject: RE: Why FEC and SCC1 can not work at the same time?
>
...
> > For FADS PPCBoot sets up both BCSR1 and BCSR4 in cpu/mpc8xx/scc.c.
> > In Linux 2.4.18 only BCSR1 is configured in arch/ppc/8xx_io/enet.c
> > Maybe configuring BCSR4 in enet.c would help.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
It all seemed, he thought, to be rather a lot of trouble to go to
just sharpen a razor blade. - Terry Pratchett, _The Light Fantastic_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-18 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 20:20 Why FEC and SCC1 can not work at the same time? Dave Ellis
2002-09-18 5:42 ` zhongqx
2002-09-18 16:40 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 7:49 zhongqx
2002-09-17 18:02 ` Ricardo Scop
2002-09-17 20:10 ` Wolfgang Denk
2002-09-18 0:31 ` zhongqx
2002-09-18 16:02 ` Rick Hunnicutt
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=20020918164010.D32BAFA8D@denx.denx.de \
--to=wd@denx.de \
--cc=DGE@sixnetio.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=zhongqx@guoguang.com.cn \
/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).