netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [PATCH 3/5] ucc_geth: eliminate max-speed, change interface-type to phy-connection-type
Date: Fri, 18 May 2007 10:33:02 -0500	[thread overview]
Message-ID: <20070518103302.476b0f04.kim.phillips@freescale.com> (raw)
In-Reply-To: <24CEBCE5-8E12-4D08-A657-24BA8688EE5D@kernel.crashing.org>

On Fri, 18 May 2007 09:07:42 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:

> 
> On May 17, 2007, at 8:53 PM, Jeff Garzik wrote:
> 
> > Kim Phillips wrote:
> >> On Tue, 15 May 2007 17:45:19 -0400
> >> Jeff Garzik <jeff@garzik.org> wrote:
> >>> Kim Phillips wrote:
> >>>> It was agreed that phy-connection-type was a better name for
> >>>> the interface-type property, so this patch renames it.
> >>>>
> >>>> Also, the max-speed property name was determined too generic,
> >>>> and is therefore eliminated in favour of phy-connection-type
> >>>> derivation logic.
> >>>>
> >>>> includes corrections to copyright text.
> >>>>
> >>>> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> >>>> ---
> >>>>  drivers/net/ucc_geth.c     |   40 +++++++++++++++ 
> >>>> +------------------------
> >>>>  drivers/net/ucc_geth_mii.c |    9 +++++----
> >>>>  drivers/net/ucc_geth_mii.h |   10 +++++-----
> >>>>  3 files changed, 26 insertions(+), 33 deletions(-)
> >>> applied to #upstream
> >>>
> >> just to be clear; only the mpc8323e-mds board works on your  
> >> current #upstream-{fixes,linus}.
> >> The mpc8323e-rdb and mpc8360e-mds require
> >> phylib: add the ICPlus IP175C PHY driver
> >> and phylib: enable RGMII-ID on the Marvell m88e1111 PHY
> >> respectively in order to work.
> >> I'm ok with the SGMII patches:
> >> phylib: m88e1111: enable SGMII mode
> >> gianfar: add support for SGMII
> >> staying on #upstream, but 2 out of 3 boards are currently broken  
> >> for #upstream-{fixes,linus}.
> >
> > New hardware support is always "broken" until merged.  Nonetheless  
> > it is still new and outside the merge window.
> 
> I think new is a little relative here.  The MPC8232-RDB & MPC8360E- 
> MDS boards worked with 2.6.21 and the UCC. They had support for the  
> PHYs that Kim's listed built directly into the ucc driver and not as  
> part of the phy lib.  Since we've moved to using the phy lib in  
> 2.6.22 we've broken these boards since their PHY drivers aren't  
> currently in linus's tree.
> 
> Kim, correct me if I'm wrong.
> 

thanks for clarifying that - it is indeed the case.

Kim

  reply	other threads:[~2007-05-18 15:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11 23:25 [PATCH 3/5] ucc_geth: eliminate max-speed, change interface-type to phy-connection-type Kim Phillips
2007-05-15 21:45 ` Jeff Garzik
2007-05-15 22:26   ` Kim Phillips
2007-05-18  1:53     ` Jeff Garzik
2007-05-18 14:07       ` Kumar Gala
2007-05-18 15:33         ` Kim Phillips [this message]
2007-05-23 13:18           ` Kumar Gala

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=20070518103302.476b0f04.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --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).