MPC82xx enet on SCC3

Hi all,

as far as I understand, my kernel (2.4.24 from ELDK3.0) is not
prepared for Ethernet on SCC3 of the MPC82xx.
It seems to be necessary to modify arch/ppc/8260_io/enet.c
Am I right?
Is there anyone who has done this already?

Thanks in advance,
Oliver

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

On Aug 12, 2004, at 10:29 AM, Oliver Fuchs wrote:

as far as I understand, my kernel (2.4.24 from ELDK3.0) is not
prepared for Ethernet on SCC3 of the MPC82xx.

It depends completely on how you chose the multiplex
the IO pins.  There are quite a few combinations, the
well known ones (for currently supported configurations)
are already part of the file.

It seems to be necessary to modify arch/ppc/8260_io/enet.c
Am I right?
Is there anyone who has done this already?

An #ifdef and two lines of #defines should be all you need,
unless you have some special BSCR or other set up needed.


	-- Dan


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

From:           	Dan Malek <redacted>
Subject:        	Re: MPC82xx enet on SCC3

quoted

as far as I understand, my kernel (2.4.24 from ELDK3.0) is not
prepared for Ethernet on SCC3 of the MPC82xx.

An #ifdef and two lines of #defines should be all you need,
unless you have some special BSCR or other set up needed.

Ok, it was a little bit more, but I have it.
I have modified arch/ppc/config.in and arch/ppc/8260_io/enet.c so
that it fits to SCC1-4 w/o further modifications there.

I would contribute this, if anyone wants to use it.
But as Wolfgang has mentioned frequently, it only makes sense to
contribute a patch that aplies to the latest CVS version.
Is there any chance to get the latest CVS version by HTTP or FTP?

Oliver

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

On Aug 16, 2004, at 10:00 AM, Oliver Fuchs wrote:

Ok, it was a little bit more, but I have it.

Apologies, I had FCC on the brain.

I have modified arch/ppc/config.in and arch/ppc/8260_io/enet.c so
that it fits to SCC1-4 w/o further modifications there.

Has anyone ever taken the patch I posted for multiple SCC Enet
support and brought it up to date?  That would have solved this
problem as well.  I've given to several people, all promising to
update it and send it back (because they actually had hardware
to test it and I don't any longer).

I would contribute this, if anyone wants to use it.

Just send it to me and I'll get it into some source base :-)

	-- Dan


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

From:           	Dan Malek <redacted>

Apologies, I had FCC on the brain.

never mind

quoted

I have modified arch/ppc/config.in and arch/ppc/8260_io/enet.c so
that it fits to SCC1-4 w/o further modifications there.

The idea is to have some board specific defines within
arch/ppc/platforms/<board>.h

like this:
--snip--
/* defines for arch/ppc/8260_io/enet.c */

#define PB_ENET_RXD      ((uint)0x00020000)
#define PD_ENET_RXD      ((uint)0x00000000)

#define PB_ENET_TXD	     ((uint)0x00000000)
#define PD_ENET_TXD      ((uint)0x00000080)

#define PC_ENET_CLSN     ((uint)0x00100000)

#define PC_ENET_TXCLK    ((uint)0x00000020)
#define PC_ENET_RXCLK    ((uint)0x00000010)

#define PB_ENET_LBK      ((uint)0x00400000)


#define CMXSCR_RS3CS_CLK5  0x00002000	/* SCC3 Rx Clock Source CLK5 */
#define CMXSCR_TS3CS_CLK6  0x00000500	/* SCC3 Tx Clock Source CLK6 */

#define CMX_CLK_ROUTE	((uint)(CMXSCR_RS3CS_CLK5 | CMXSCR_TS3CS_CLK6))

/* #define SCC_ENET_PIN_ENABLE */
--snap--

mind the defines for RxD and TxD for both ports B and D
it's needed to decide which port is used
SCC_ENET_PIN_ENABLE could be used to setup LBK, FDE or DSQ

Just send it to me and I'll get it into some source base :-)

here you are
It's tested for SCC3.


Best regards,
Oliver Fuchs