From: Fabio <pozzi.fabio@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Andy Fleming <afleming@freescale.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Help initialize phy-less ethernet in 2.6.38
Date: Tue, 3 Apr 2012 13:04:48 +0200 [thread overview]
Message-ID: <CAP-cLV4VW52fWvTr+6f441Jfr5WkPwtDjDbsoy0anKJbhnYxmQ@mail.gmail.com> (raw)
In-Reply-To: <4F74C65A.2000006@freescale.com>
> So it's old arch/ppc stuff. =C2=A0Now fs_platform_info is driver-internal=
and
> info comes from the device tree. =C2=A0You shouldn't touch the struct dir=
ectly.
Now I moved all the initialization functions to the platform driver in
arch/powerpc/platform/82xx and the external ethernet on FCC2 still
works, so at least it seems that
the problem is related to the fixed-link initialization of FCC1.
>>> Looking at the code, though, I'm not sure if this stuff still works --
>>> e.g. I don't see where any fields of fixed-link but the ID are used, or
>>> what's supposed to happen when of_phy_connect_fixed_link() calls
>>> phy_connect().
The fixed-link fields are used inside arch/powerpc/sysdev/fsl_soc.c in
the function
of_add_fixed_phys.
I'm trying to understand what I am missing to configure or initialize
to get the same behaviour as in the old kernel but I failed to do so
until now.
If you have any suggestion it will be of great help for me.
Thanks in advance
--=20
Fabio Pozzi
prev parent reply other threads:[~2012-04-03 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 16:13 Help initialize phy-less ethernet in 2.6.38 Fabio
2012-03-29 18:35 ` Scott Wood
2012-03-29 19:56 ` Fabio
2012-03-29 20:30 ` Scott Wood
2012-04-03 11:04 ` Fabio [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=CAP-cLV4VW52fWvTr+6f441Jfr5WkPwtDjDbsoy0anKJbhnYxmQ@mail.gmail.com \
--to=pozzi.fabio@gmail.com \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@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;
as well as URLs for NNTP newsgroup(s).