From: Ian Campbell <ijc@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] net/designware: call phy_connect_dev() to properly setup phylib device
Date: Wed, 14 May 2014 08:29:48 +0100 [thread overview]
Message-ID: <1400052588.27638.11.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20140513111901.GO22182@bill-the-cat>
On Tue, 2014-05-13 at 07:19 -0400, Tom Rini wrote:
> On Tue, May 13, 2014 at 11:19:13AM +0100, Ian Campbell wrote:
> > On Mon, 2014-05-12 at 21:53 -0400, Tom Rini wrote:
> > > On Mon, Apr 28, 2014 at 08:14:05PM +0100, Ian Campbell wrote:
> > >
> > > > This sets up the linkage from the phydev back to the ethernet device. This
> > > > symptom of not doing this which I noticed was:
> > > > <NULL> Waiting for PHY auto negotiation to complete....
> > > > rather than:
> > > > dwmac.1c50000 Waiting for PHY auto negotiation to complete....
> > > >
> > > > Signed-off-by: Ian Campbell <ijc@hellion.org.uk>
> > > > Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
> > >
> > > Applied to u-boot/master, thanks!
> >
> > Thanks, have you also seen "[PATCH v3 0/5] net/designware: fixes for
> > data cache, phylib and burst size" which included this and some other
> > (far more critical, since designware is currently unusable on ARM)
> > fixes?
>
> For the moment I've tossed all of the rest of them over to Albert to
> grab along with the sunxi stuff.
OK, thanks. Does that mean they should be delegated to him in patchwork
(because they still say trini)?
> Albert, if you're uncomfortable there
> I can pick them up instead, thanks!
Cheers,
Ian.
next prev parent reply other threads:[~2014-05-14 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 19:14 [U-Boot] [PATCH] net/designware: call phy_connect_dev() to properly setup phylib device Ian Campbell
2014-05-13 1:53 ` [U-Boot] " Tom Rini
2014-05-13 10:19 ` Ian Campbell
2014-05-13 11:19 ` Tom Rini
2014-05-14 7:29 ` Ian Campbell [this message]
2014-05-14 15:20 ` Tom Rini
2014-05-21 18:44 ` Ian Campbell
2014-05-21 19:33 ` Tom Rini
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=1400052588.27638.11.camel@dagon.hellion.org.uk \
--to=ijc@hellion.org.uk \
--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