From: Dirk Brandewie <dirk.j.brandewie@intel.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Florian Fainelli <ffainelli@freebox.fr>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] e1000: add support for Marvell Alaska M88E1118R PHY
Date: Thu, 20 Jan 2011 10:49:19 -0800 [thread overview]
Message-ID: <1295549359.7387.30.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTinDh-ZnrZy3f5H72+FuNwvbnY-BnCns17+cpR=Z@mail.gmail.com>
On Wed, 2011-01-19 at 22:51 -0800, Jeff Kirsher wrote:
> On Wed, Jan 19, 2011 at 01:09, Florian Fainelli <ffainelli@freebox.fr> wrote:
> > From: Florian Fainelli <ffainelli@freebox.fr>
> >
> > This patch adds support for Marvell Alask M88E188R PHY chips. Support for
> > other M88* PHYs is already there, so there is nothing more to add than its
> > PHY id.
> >
> > Signed-off-by: Florian Fainelli <ffainelli@freebox.fr>
> > CC: Dirk Brandewie <dirk.j.brandewie@intel.com>
> > CC: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > ---
>
> The patch itself looks fine. I am concerned about validation.
>
> Dirk - is there a chance that the ce4100 will use this PHY? If so,
> can you cover the validation?
Florian is working on a CE4100 based platform. It looks like they used
a different PHY from the Flacon Falls reference platform. I can't
directly test this patch since I don't have their hardware. I will be
testing .38-rc1 next week on falcon falls.
I think the best we can do without the hardware is to compare the data
sheet for the new PHY with the PHYs already supported and make sure they
are compatible. If the datasheets match up for the features the driver
is using this seems pretty low risk IMHO.
--Dirk
>
> For now I will add this to my net-next tree while I await word from Dirk.
>
next prev parent reply other threads:[~2011-01-20 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 9:09 [PATCH] e1000: add support for Marvell Alaska M88E1118R PHY Florian Fainelli
2011-01-20 6:51 ` Jeff Kirsher
2011-01-20 18:49 ` Dirk Brandewie [this message]
2011-01-21 16:27 ` Florian Fainelli
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=1295549359.7387.30.camel@localhost.localdomain \
--to=dirk.j.brandewie@intel.com \
--cc=davem@davemloft.net \
--cc=ffainelli@freebox.fr \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.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).