From: "Dennis Khoo" <dkhoo@atmxdsl.com>
To: "Jaap-Jan Boor" <jjboor@aimsys.nl>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problem using both mpc857dsl fec and scc1
Date: Fri, 5 Dec 2003 10:53:06 -0800 [thread overview]
Message-ID: <000b01c3bb61$0c4bec70$7ec7c7c7@dkhoo> (raw)
In-Reply-To: 1070622713.28153.5.camel@linpc003.aimsys.nl
Hi Jaap-Jan,
> I would say to double check your parallel port I/O settings
Thanks
Actually, when I switched to ramdisk instead of NFS, then both SCC1 and FEC
work together. Maybe some timimg issue in the fec.c code affected by
packets coming in initially?
Thanks again
Dennis Khoo
Software Engineer
Adapcom, INC
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-12-05 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 17:48 ram root filesystem AlessandroPPC
2003-12-03 18:16 ` Wolfgang Denk
2003-12-04 10:12 ` Use of several CFI flash chips physically mapped in memory Gérard Guével
2003-12-05 8:36 ` R: ram root filesystem AlessandroPPC
2003-12-04 0:08 ` problem using both mpc857dsl fec and scc1 Dennis Khoo
2003-12-05 11:11 ` Jaap-Jan Boor
2003-12-05 18:53 ` Dennis Khoo [this message]
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='000b01c3bb61$0c4bec70$7ec7c7c7@dkhoo' \
--to=dkhoo@atmxdsl.com \
--cc=jjboor@aimsys.nl \
--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).