From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] micrel: add support for KSZ8041RNLI
Date: Tue, 10 Dec 2013 21:21:38 +0400 [thread overview]
Message-ID: <52A74DA2.40201@cogentembedded.com> (raw)
In-Reply-To: <CAMuHMdXdvF+N0+b0Mo3DO4Vj3NCymh-ySU_SMRATFUekSfnaRg@mail.gmail.com>
Hello.
On 10-12-2013 17:19, Geert Uytterhoeven wrote:
>> Renesas R-Car development boards use KSZ8041RNLI PHY which for some reason has
>> ID of 0x00221537 that is not documented for KSZ8041-family PHYs and does not
>> match the documented ID of 0x0022151x (where 'x' is the revision). We have
>> to add the new #define PHY_ID_* and new ksphy_driver[] entry, almost the same
>> as KSZ8041 one, differing only in the 'phy_id' and 'name' fields.
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Thanks. Though it's not the last version probably...
> I don't seem to get "net eth0: Receive FIFO Overflow" anymore after applying
> this patch.
Cool.
So you also enabled the Micrel PHY driver in .config? Asking because it's
not in 'koelsch_defconfig' or any other R-Car defconfig yet...
> Gr{oetje,eeting}s,
>
> Geert
WBR, Sergei
next prev parent reply other threads:[~2013-12-10 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 23:20 [PATCH] micrel: add support for KSZ8041RNLI Sergei Shtylyov
2013-12-10 13:19 ` Geert Uytterhoeven
2013-12-10 17:21 ` Sergei Shtylyov [this message]
2013-12-10 19:05 ` Geert Uytterhoeven
2013-12-11 3:26 ` David Miller
2013-12-11 15:39 ` Sergei Shtylyov
2013-12-11 18:58 ` David Miller
2013-12-11 21:28 ` Sergei Shtylyov
2013-12-11 21:11 ` David Miller
2013-12-11 23:02 ` Sergei Shtylyov
2013-12-11 22:10 ` David Miller
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=52A74DA2.40201@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.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).