From: Kumar Gala <kumar.gala@freescale.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Netdev <netdev@oss.sgi.com>,
inuxppc-embedded List <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] gianfar: Update Marvell PHY name
Date: Thu, 10 Mar 2005 01:30:02 -0600 [thread overview]
Message-ID: <1047a05d13208f6f49df5590040d3c16@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503040150480.16127@blarg.somerset.sps.mot.com>
Jeff,
Just wondering if this got lost? Might be moot depending what=20
likelihood of getting Andy's PHY Abstraction Layer changes into the=20
kernel.
- kumar
On Mar 4, 2005, at 1:55 AM, Kumar Gala wrote:
> Jeff,
>
> This patch updates the name identifier to list both of the Marvell =
PHYs
> that are supported.
>
> Signed-off-by: Kumar Gala <kumar.gala@freescale.com>
>
> ---
> diff -Nru a/drivers/net/gianfar_phy.c b/drivers/net/gianfar_phy.c
> --- a/drivers/net/gianfar_phy.c 2005-03-02 14:20:27 -06:00
> +++ b/drivers/net/gianfar_phy.c 2005-03-02 14:20:27 -06:00
> @@ -572,7 +572,7 @@
> =A0static struct phy_info phy_info_marvell =3D {
> =A0=A0=A0=A0=A0=A0=A0 .phy_id =A0=A0=A0=A0=A0=A0=A0 =3D 0x01410c00,
> =A0=A0=A0=A0=A0=A0=A0 .phy_id_mask=A0=A0=A0 =3D 0xffffff00,
> -=A0=A0=A0=A0=A0=A0 .name=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =3D "Marvell =
88E1101",
> +=A0=A0=A0=A0=A0=A0 .name=A0=A0 =A0=A0=A0=A0=A0=A0=A0 =3D "Marvell =
88E1101/88E1111",
> =A0=A0=A0=A0=A0=A0=A0 .features=A0=A0=A0=A0=A0=A0 =3D =
MII_GBIT_FEATURES,
> =A0=A0=A0=A0=A0=A0=A0 .config_aneg=A0=A0=A0 =3D &marvell_config_aneg,
> =A0=A0=A0=A0=A0=A0=A0 .read_status=A0=A0=A0 =3D &marvell_read_status,
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
next prev parent reply other threads:[~2005-03-10 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 7:55 [PATCH] gianfar: Update Marvell PHY name Kumar Gala
2005-03-10 7:30 ` Kumar Gala [this message]
2005-06-26 21:59 ` Jeff Garzik
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=1047a05d13208f6f49df5590040d3c16@freescale.com \
--to=kumar.gala@freescale.com \
--cc=jgarzik@pobox.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=netdev@oss.sgi.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).