From: Dan Malek <dan@netx4.com>
To: Ruedi.Hofer@ascom.ch
Cc: linuxppc-embedded@lists.linuxppc.org, kernel@linux01.hasler.ascom.ch
Subject: Re: MPC860T
Date: Thu, 27 Apr 2000 11:38:17 -0400 [thread overview]
Message-ID: <39085EE9.6052CE60@embeddededge.com> (raw)
In-Reply-To: 0FTO0083YCJPTE@pmdf-it.hasler.ascom.ch
Ruedi.Hofer@ascom.ch wrote:
> After some success with the native 860, I moved now to the 860T
> on the FADS evaluation board.
You poor soul.....
> 2. I'm not able to compile the kernel with only FEC enabled.
> (commproc.h reports: #error, undefined config!)
That's interesting. What kernel are you using?
> 3. Is it possible to use SCC1 enet and FEC simultaneously.
Of course. I use it as a firewall/gateway/router.....
> Can someone provide patches or howto's?
Get the 2.2.13 kernel from MontaVista's ftp site.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-27 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-27 13:11 MPC860T Ruedi.Hofer
2000-04-27 15:38 ` Dan Malek [this message]
2000-04-28 1:29 ` MPC860T duncanp
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=39085EE9.6052CE60@embeddededge.com \
--to=dan@netx4.com \
--cc=Ruedi.Hofer@ascom.ch \
--cc=kernel@linux01.hasler.ascom.ch \
--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).