From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net: Multiple updates/enhancements to designware.c
Date: Fri, 1 Jun 2012 14:55:42 +0200 [thread overview]
Message-ID: <201206011455.42774.sr@denx.de> (raw)
In-Reply-To: <201205091136.56591.sr@denx.de>
Joe,
On Wednesday 09 May 2012 11:36:56 Stefan Roese wrote:
> > > +++ b/include/configs/spear-common.h
> > > @@ -38,6 +38,7 @@
> > >
> > > #define CONFIG_NET_MULTI
> > > #define CONFIG_PHY_RESET_DELAY 10000 /*
>
> in usec */
>
> > > #define CONFIG_DW_AUTONEG
> > >
> > > +#define CONFIG_PHY_GIGE /* Include GbE speed/duplex
>
> detection */
>
> > Shouldn't this come in a separate patch?
>
> Not sure. This change is needed for this change in the designware driver to
> really work with 1000mbps links:
>
> - Use common functions miiphy_speed()& miiphy_duplex() to read
> link status from PHY.
>
> Splitting it into a separate commit will result in a non working ethernet
> driver for such links. Even though it should still compile and be git
> bisectable. I would prefer to keep it in one patch.
Are you okay with this patch? If yes, perhaps it would be best if I would push
this patch with the other SPEAr platform patches upstream. What do you think?
Can I have your Acked-by?
Thanks,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2012-06-01 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 7:29 [U-Boot] [PATCH] net: Multiple updates/enhancements to designware.c Stefan Roese
2012-05-09 9:29 ` Amit Virdi
2012-05-09 9:36 ` Stefan Roese
2012-06-01 12:55 ` Stefan Roese [this message]
2012-06-04 19:24 ` Joe Hershberger
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=201206011455.42774.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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