linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* MPC860T
@ 2000-04-27 13:11 Ruedi.Hofer
  2000-04-27 15:38 ` MPC860T Dan Malek
  2000-04-28  1:29 ` MPC860T duncanp
  0 siblings, 2 replies; 3+ messages in thread
From: Ruedi.Hofer @ 2000-04-27 13:11 UTC (permalink / raw)
  To: linuxppc-embedded; +Cc: kernel

[-- Attachment #1: Type: TEXT/PLAIN, Size: 657 bytes --]

Hi

After some success with the native 860, I moved now to the 860T
on the FADS evaluation board.

With this test setup, I'd like to do some internetworking tests.
(like routing ...)

For that reason I need the FEC working as well as the SCC1 enet.

Facts:

1. The SCC1 enet compiles and runs ok on its own.

2. I'm not able to compile the kernel with only FEC enabled.
 (commproc.h reports: #error, undefined config!)

3. Is it possible to use SCC1 enet and FEC simultaneously.
 (fec.c has a comment like:
 If using multiple enets on 8xx, this needs some work!)

Has someone already done this work??

Can someone provide patches or howto's?

Thanx, Ruedi


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: MPC860T
  2000-04-27 13:11 MPC860T Ruedi.Hofer
@ 2000-04-27 15:38 ` Dan Malek
  2000-04-28  1:29 ` MPC860T duncanp
  1 sibling, 0 replies; 3+ messages in thread
From: Dan Malek @ 2000-04-27 15:38 UTC (permalink / raw)
  To: Ruedi.Hofer; +Cc: linuxppc-embedded, kernel


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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: MPC860T
  2000-04-27 13:11 MPC860T Ruedi.Hofer
  2000-04-27 15:38 ` MPC860T Dan Malek
@ 2000-04-28  1:29 ` duncanp
  1 sibling, 0 replies; 3+ messages in thread
From: duncanp @ 2000-04-28  1:29 UTC (permalink / raw)
  To: Ruedi.Hofer; +Cc: linuxppc-embedded, kernel


On 27 Apr, Ruedi.Hofer@ascom.ch wrote:
> Hi
>
> After some success with the native 860, I moved now to the 860T
> on the FADS evaluation board.
>
> With this test setup, I'd like to do some internetworking tests.
> (like routing ...)
>
> For that reason I need the FEC working as well as the SCC1 enet.
>
> Facts:
>
> 1. The SCC1 enet compiles and runs ok on its own.
>
> 2. I'm not able to compile the kernel with only FEC enabled.
>  (commproc.h reports: #error, undefined config!)

This is a bit strange - i'm doing just this with no problems. Could you
post a copy of your .config?

>
> 3. Is it possible to use SCC1 enet and FEC simultaneously.
>  (fec.c has a comment like:
>  If using multiple enets on 8xx, this needs some work!)

This jsut refers to setting MAC addresses for the interfaces. The board
info structures for all boards in the current kernel only include 1 MAC
address, so the 1st interface (the SCC) uses this address, and the MAC
address for the 2nd interface (i.e. the fec) is generated by
modifying the address in the board info struct a bit. This is probably
not neccesary for the router config you are talking about - as long as
you are not going to have both interfaces plugged into the same network
segmenet, its ok for them to share the same MAC address.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-04-28  1:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-04-27 13:11 MPC860T Ruedi.Hofer
2000-04-27 15:38 ` MPC860T Dan Malek
2000-04-28  1:29 ` MPC860T duncanp

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).