From: Grant Likely <grant.likely@secretlab.ca>
To: Johns Daniel <johns.daniel@gmail.com>
Cc: linuxppc-dev@ozlabs.org, afleming@freescale.com
Subject: Re: TSEC/MDIO bug in recent kernels
Date: Tue, 10 Mar 2009 17:57:51 -0600 [thread overview]
Message-ID: <fa686aa40903101657w1232097flb3535f911ef81c1e@mail.gmail.com> (raw)
In-Reply-To: <ba5d9360903101555o3d6f5932k9292a006328c7161@mail.gmail.com>
On Tue, Mar 10, 2009 at 4:55 PM, Johns Daniel <johns.daniel@gmail.com> wrot=
e:
> For those of you who are running into this error:
> =A0 =A0 =A0 =A024520:01 not found
> =A0 =A0 =A0 =A0eth0: Could not attach to PHY
> =A0 =A0 =A0 =A0IP-Config: Failed to open eth0
> =A0 =A0 =A0 =A0IP-Config: Device `eth0' not found.
>
> There is a bug in recent kernels. I found it in 2.6.28.7:
> =A0 =A0 =A0 =A0linux/arch/powerpc/sysdev/fsl_soc.c:
> for_each_compatible_node(np, "mdio", "gianfar");
> should be:
> =A0 =A0 =A0 =A0linux/arch/powerpc/sysdev/fsl_soc.c:
> for_each_compatible_node(np, "mdio", "gianfar")
This code is gone in what will become 2.6.29, but the fix can be
backported into the stable tree. Do you want to generate and send the
patch (and get your name in the commit message)? Send the patch to
afleming@freescale.com, linuxppc-dev@ozlabs.org and to
stable@kernel.org. Make sure you specify that this is applicable for
2.6.28 only.
g.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-03-10 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 22:53 TSEC/MDIO bug in recent kernels Johns Daniel
2009-03-10 22:55 ` Johns Daniel
2009-03-10 23:57 ` Grant Likely [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=fa686aa40903101657w1232097flb3535f911ef81c1e@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=afleming@freescale.com \
--cc=johns.daniel@gmail.com \
--cc=linuxppc-dev@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).