From: Michael Habermann <MHabermann@gmx.de>
To: o_y <o_yahav@netvision.net.il>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC860T FEC problem
Date: Sun, 08 Sep 2002 09:06:33 +0200 [thread overview]
Message-ID: <3D7AF6F9.6010408@gmx.de> (raw)
In-Reply-To: MBBBIOFIICDAPDMKHBDEKEDLCAAA.o_yahav@netvision.net.il
o_y wrote:
> that ppcboot uses , so the ENABLE led is on too.
> The device isn't working even when i use ppcboot (i configured ppcboot to
> use it).
If you use a FADS, you need to check that the dip switches belonging to
the FEC are in the default position according to the users manual.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-09-08 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-07 16:59 MPC860T FEC problem o_y
2002-09-07 17:14 ` Wolfgang Denk
2002-09-08 7:06 ` Michael Habermann [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-08 20:52 o_y
2002-09-09 14:58 Rod Boyce
2002-09-09 15:29 ` 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=3D7AF6F9.6010408@gmx.de \
--to=mhabermann@gmx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=o_yahav@netvision.net.il \
/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).