netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claudiu Manoil <claudiu.manoil@freescale.com>
To: "Émeric Vigier" <emeric.vigier@savoirfairelinux.com>,
	netdev@vger.kernel.org, "David Miller" <davem@davemloft.net>
Cc: "Cane, Romeo (EXT-Other PT/Amadora)" <romeo.cane.ext@coriant.com>
Subject: Re: powerpc: net: gianfar ethernet broken on linux-3.10.29?
Date: Wed, 26 Mar 2014 15:02:41 +0200	[thread overview]
Message-ID: <5332CFF1.5080402@freescale.com> (raw)
In-Reply-To: <1385350976.279693.1395775567178.JavaMail.root@mail>

On 3/25/2014 9:26 PM, Émeric Vigier wrote:
> Hi guys,
>
> I work on a Freescale MPC8347 custom board. I ported u-boot-v2014.01 on it. My config is attached.
> I ported linux-3.2.52 (long-term). DTS is attached.
>
[...]
>
> Do you guys see what could be wrong in my config?
> Or what has changed in linux-3.{4,6,8,10} that could break my ethernet?
>
> thanks,
> Emeric
>

Hi Emeric,

Thanks for the detailed logs.
You may refer to Romeo's issue:
http://permalink.gmane.org/gmane.linux.network/309587

There's this stable fix for the (older) TSEC controllers:
commit 5eaedf31319d5f80eaaee1eec8dd18c0b452f0d1
("gianfar: Add backwards compatible Single Queue mode polling")

that for some reason was not included in kernel 3.10
(but it was included in kernel 3.11).

Hi David,
Can we have this gianfar fix included in kernel 3.10 as well?
Is there anything I can do to help with this?

Thanks and regards,
Claudiu

  reply	other threads:[~2014-03-26 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2067855247.249513.1395772774452.JavaMail.root@mail>
2014-03-25 19:26 ` powerpc: net: gianfar ethernet broken on linux-3.10.29? Émeric Vigier
2014-03-26 13:02   ` Claudiu Manoil [this message]
2014-03-26 14:04     ` Émeric Vigier

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=5332CFF1.5080402@freescale.com \
    --to=claudiu.manoil@freescale.com \
    --cc=davem@davemloft.net \
    --cc=emeric.vigier@savoirfairelinux.com \
    --cc=netdev@vger.kernel.org \
    --cc=romeo.cane.ext@coriant.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).