linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Munoz <carlos@kenati.com>
To: linuxppc-embedded@ozlabs.org
Subject: Problems with fcc_enet driver for MPC8248 (2.6.12)
Date: Thu, 17 Nov 2005 15:39:59 -0800	[thread overview]
Message-ID: <437D14CF.5070000@kenati.com> (raw)

I'm working on an embedded board that is currently running kernel 2.4.28 
without any problems. However, I am trying to upgrade from kernel 2.4.28 
to kernel 2.6.12 and I'm unable to get the fcc_enet driver to work 
properly.
The fcc ports are connected to ethernet phy devices. The receive and 
transmitted data out of the ethernet phy devices is all 0xff.

I tried using the fcc_enet driver from the 2.4.28 kernel on the 2.6.12 
kernel but get the same results. This leads me to believe that the core 
initialization of the MPC8248 has changed on kernel 2.6.12.

Has anyone got the  fcc ports to work properly on the 2.6.12 kernel ? If 
yes, how ? Did the MPC8248 core initialization change ?

Thanks,


Carlos Munoz

                 reply	other threads:[~2005-11-18  0:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=437D14CF.5070000@kenati.com \
    --to=carlos@kenati.com \
    --cc=linuxppc-embedded@ozlabs.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).