FEC support for 8260 in kernel 2.4.25

FEC support for 8260 in kernel 2.4.25

[T Michael Turney]

Hi Folks,
This is my first posting on this list.

I am working on a kernel port to an 8260 board that
has all three FCCs wired up to PHYs (BCM5221).

The first FCC is working fine, but I haven't been
successful with getting FCC2 and FCC3 going yet.

Is anybody out there successfully using the 2.4.x
fcc_enet.c code with all three channels active?

Cheers,
T.mike

Tools Made Tough
Project Consultant
(o) 760.728.5401
(c) 760.415.8792

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

Re: FEC support for 8260 in kernel 2.4.25

[Ricardo Scop]

Hello T,

Friday, April 23, 2004, 8:23:37 PM, you wrote:

TMT> I am working on a kernel port to an 8260 board that
TMT> has all three FCCs wired up to PHYs (BCM5221).

TMT> The first FCC is working fine, but I haven't been
TMT> successful with getting FCC2 and FCC3 going yet.

TMT> Is anybody out there successfully using the 2.4.x
TMT> fcc_enet.c code with all three channels active?

Yes!

Cheers,

-Scop.

Best regards,
 Ricardo                            mailto:scop@digitel.com.br

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

Re: FEC support for 8260 in kernel 2.4.25

[Dan Malek]

On Apr 23, 2004, at 7:23 PM, T Michael Turney wrote:

> Is anybody out there successfully using the 2.4.x
> fcc_enet.c code with all three channels active?

Sure.

There are lots of I/O pins that have to be configured correctly for
clocks and data lines.  It can take a while to get this right, but the
driver has the typical configurations ready to go out of the box.

	-- Dan


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

Re: FEC support for 8260 in kernel 2.4.25

[Jaap-Jan Boor]

On 24-apr-04, at 1:23, T Michael Turney wrote:

>
> Hi Folks,
> This is my first posting on this list.
>
> I am working on a kernel port to an 8260 board that
> has all three FCCs wired up to PHYs (BCM5221).
>
> The first FCC is working fine, but I haven't been
> successful with getting FCC2 and FCC3 going yet.
>
> Is anybody out there successfully using the 2.4.x
> fcc_enet.c code with all three channels active?

I use 2, FCC1 and FCC3 on a dual port phy.
just make sure you program the gpio ports
correctly.

>
> Cheers,
> T.mike
>
> Tools Made Tough
> Project Consultant
> (o) 760.728.5401
> (c) 760.415.8792
>


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

RE: FEC support for 8260 in kernel 2.4.25

[Andrew Williams]

-- Fourth Attempt.. hoping to have disabled HTML output in Outlook --

Not just the GPIO pins, be sure to note the different
clock sources. (Which in the code is clearly labeled as
"This is board specific", but then goes on to declare
constant values in the common fcc_enet.c file).

  This bothered me enough that I changed the fcc_enet
files from:

#define PC_F1RXCLK      ((uint)0x00000800)
#define PC_F1TXCLK      ((uint)0x00000400)
#define CMX1_CLK_ROUTE  ((uint)0x3e000000)

to

#ifndef PC_F1RXCLK
#define PC_F1RXCLK      ((uint)0x00000800)
#endif
#ifndef PC_F1TXCLK
#define PC_F1TXCLK      ((uint)0x00000400)
#endif
#ifndef CMX1_CLK_ROUTE
#define CMX1_CLK_ROUTE  ((uint)0x3e000000)
#endif

 (repeat for all 3 interfaces)

I know it looks a bit kludgy, but you can now declare board
specific values in your platform/<platform>.h file, and have these
override the current default hard coded values. Furthermore this
change won't break any existing platforms. :o)

One other potential 'gotcha' is if you have different FPSMR values
depending on the interface. The current code (2.4.22) limits you to
a single value that applies to all three interfaces. I worked around
this one, by adding a field to 'fcc_info' for the fpsmr. Then in the
declaration of 'fcc_ports' I once again used conditional
compiles to allow FPSMR values in the platforms file to override
the default FCC_PSMR_ENCRC value.


Andrew

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

RE: FEC support for 8260 in kernel 2.4.25

[T Michael Turney]

Thanks for all the inputs I received on the original query.

Update: All FCC ports are functional at 100 Mbps, but not
at 10 Mbps.

I had made some changes to the do/while loop in fec_enet_init,
investigating this problem.  When I backed those changes out
and removed the 10Mbps traffic, the 3 FCCs started to play.

Not sure why the 10 Mbps traffic is causing problems,
the LEDs seem to indicate the PHY (BCM5221) is correctly
auto-negotiating.
Cheers,
T.mike

> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Andrew
> Williams
> Sent: Monday, April 26, 2004 11:49 AM
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: RE: FEC support for 8260 in kernel 2.4.25
>
>
>
> -- Fourth Attempt.. hoping to have disabled HTML output in Outlook --
>
> Not just the GPIO pins, be sure to note the different
> clock sources. (Which in the code is clearly labeled as
> "This is board specific", but then goes on to declare
> constant values in the common fcc_enet.c file).
>
>   This bothered me enough that I changed the fcc_enet
> files from:
>
> #define PC_F1RXCLK      ((uint)0x00000800)
> #define PC_F1TXCLK      ((uint)0x00000400)
> #define CMX1_CLK_ROUTE  ((uint)0x3e000000)
>
> to
>
> #ifndef PC_F1RXCLK
> #define PC_F1RXCLK      ((uint)0x00000800)
> #endif
> #ifndef PC_F1TXCLK
> #define PC_F1TXCLK      ((uint)0x00000400)
> #endif
> #ifndef CMX1_CLK_ROUTE
> #define CMX1_CLK_ROUTE  ((uint)0x3e000000)
> #endif
>
>  (repeat for all 3 interfaces)
>
> I know it looks a bit kludgy, but you can now declare board
> specific values in your platform/<platform>.h file, and have these
> override the current default hard coded values. Furthermore this
> change won't break any existing platforms. :o)
>
> One other potential 'gotcha' is if you have different FPSMR values
> depending on the interface. The current code (2.4.22) limits you to
> a single value that applies to all three interfaces. I worked around
> this one, by adding a field to 'fcc_info' for the fpsmr. Then in the
> declaration of 'fcc_ports' I once again used conditional
> compiles to allow FPSMR values in the platforms file to override
> the default FCC_PSMR_ENCRC value.
>
>
> Andrew
>


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