From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: M B <super.firetwister@googlemail.com>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Get new_emac driver running on 405EP
Date: Tue, 15 Apr 2008 07:02:41 +1000 [thread overview]
Message-ID: <1208206961.6958.180.camel@pasglop> (raw)
In-Reply-To: <6a6049b80804141038k77ac361cl11f50bc9d890c6a2@mail.gmail.com>
On Mon, 2008-04-14 at 19:38 +0200, M B wrote:
> Hi,
> I'm trying to get the new_emac driver (linux 2.6.25-rc8) running on my
> 405EP board with a KSZ8721BT Micrel/Kendin PHY.
> I've already found 2 problems/missing features:
> 1) 100 retries in __emac_mdio_read for the read to complete are
> slightly too less. 101 seem to be enough. But we could add a bit more,
> because there is no negative effect for faster chips.
> 2) On the 405EP only the MDIO pin of the emac0 is pinned out, so both
> phys have to be accessed through this one. This affectes the mdio
> read/write functions.
The later can easily be described in the device-tree as it's a fairly
common setup.
> I've already hacked around this problems, but ethernet is still not working.
> After bringing up the device dmesg is flooded with this section.
> emac/plb/opb/ethernet@ef600800: link timer
> emac/plb/opb/ethernet@ef600800: mdio_read(00,01)
> emac/plb/opb/ethernet@ef600800: mdio_read -> 786d
> emac/plb/opb/ethernet@ef600800: mdio_read(00,01)
> emac/plb/opb/ethernet@ef600800: mdio_read -> 786d
>
>
> Any ideas where I should start looking?
The above is the timer polling the link, you may want to remove that
debug once it looks sane.
Ben.
next prev parent reply other threads:[~2008-04-14 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 17:38 Get new_emac driver running on 405EP M B
2008-04-14 21:02 ` Benjamin Herrenschmidt [this message]
2008-04-15 21:51 ` Markus Brunner
2008-04-16 1:43 ` Josh Boyer
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=1208206961.6958.180.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=super.firetwister@googlemail.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).