From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale FEC packet loss
Date: Thu, 6 Feb 2014 14:41:20 +0100 [thread overview]
Message-ID: <201402061441.20475.marex@denx.de> (raw)
In-Reply-To: <CAH9NwWeK17kfty-BAA9Y977BGTYBcJLRSRESrfbCvQ_BiVxa0A@mail.gmail.com>
On Thursday, February 06, 2014 at 10:42:00 AM, Christian Gmeiner wrote:
[...]
> Are there still problems with 3.13.1 kernel regarding FEC networking?
They are on 3.13.0 and I don't see any network-related fixes in 3.13.1 .
> Does this only
> affect the SabreLite?
No, this is not board-specific. This affects different boards and different MX6
CPUs.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-02-06 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 21:55 Freescale FEC packet loss Marek Vasut
2014-01-23 1:49 ` fugang.duan at freescale.com
2014-01-23 14:20 ` Marek Vasut
2014-01-24 1:28 ` fugang.duan at freescale.com
2014-01-26 18:56 ` Ben Hutchings
2014-01-26 19:12 ` Marek Vasut
2014-01-26 21:33 ` Ben Hutchings
2014-01-28 1:01 ` Marek Vasut
2014-02-06 9:42 ` Christian Gmeiner
2014-02-06 13:41 ` Marek Vasut [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-06 5:30 Christian Ege
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=201402061441.20475.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.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).