LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "KylongMu" <mqy@263.net.cn>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: Linuxppc-embedded@ozlabs.org
Subject: mpc8540 SK board FEC work now! (Thanks for Andy Fleming)
Date: Wed, 27 Jul 2005 12:10:33 +0800	[thread overview]
Message-ID: <20050727041045.34D20C362A@smtp.263.net> (raw)
In-Reply-To: <8F2178E8-C29F-412E-9F07-F81F5E40153F@freescale.com>

 
Hi Andy:
	Thanks for your help , my board's all eth ports works now ,
according the file you give out:
" arch/ppc/ platforms/85xx/mpc8540_ads.c " , I modified the TSEC ID from 0,1
to 4,5 ,  and modified
the TFEC interrupt source from 5 to 7 , after these modification , my board
can work.

Thanks a lot!

KylongMu

On Jul 26, 2005, at 01:02, KylongMu wrote:
>
> eth0 and eth1 not work, they are giga ethernet , but eth2 work well , 
> I know all of them are drived under same driver " drivers/net/gianfar* 
> ", and I checked the 8540 datasheet , because the MAC is integrated , 
> the only deferent is the PHY , the 2.4.18 kernel come with my board is 
> work well at all eth port , so I'm sure the hardware is OK

On Jul 27, 2005, at 02:26, Andy Fleming wrote:

The manual says the PHY addresses for TSEC 1 and TSEC 2 are:

TSEC1: 4
TSEC2: 5

The 8540 ADS has this configuration:

TSEC1: 0
TSEC2: 1

The correct solution would be to make a new board file for the SK board, and
properly configure everything.  However, if you insist on using the 8540 ADS
config for this, you will need to change arch/ppc/
platforms/85xx/mpc8540_ads.c so that TSEC1 and TSEC2 have their phyid
platform data fields assigned to be:

TSEC1: 4
TSEC2: 5

      reply	other threads:[~2005-07-27  4:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050726060304.AF08EC372E@smtp.263.net>
2005-07-26 18:26 ` mpc8540 SK board FEC not work! (second message) Andy Fleming
2005-07-27  4:10   ` KylongMu [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=20050727041045.34D20C362A@smtp.263.net \
    --to=mqy@263.net.cn \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=afleming@freescale.com \
    /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