From: Henri Roosen <henri.roosen@ginzinger.com>
To: <eric@nelint.com>, <fugang.duan@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: commit-3ac72b7b63d5 breaks networking on iMX28
Date: Fri, 21 Oct 2016 11:19:50 +0200 [thread overview]
Message-ID: <bc6aa851-3f52-2274-47dc-4933662648a1@ginzinger.com> (raw)
Hi,
Unfortunately commit-3ac72b7b63d5 "net: fec: align IP header in
hardware" breaks networking on an iMX28 system.
The commit seems valid for iMX6, where it is tested okay and solves the
unaligned accesses.
On iMX28 I still see unaligned accesses and networking is broken. Can
anyone confirm this?
Thanks,
Henri
________________________________
Ginzinger electronic systems GmbH
Gewerbegebiet Pirath 16
4952 Weng im Innkreis
www.ginzinger.com
Firmenbuchnummer: FN 364958d
Firmenbuchgericht: Ried im Innkreis
UID-Nr.: ATU66521089
________________________________
Kommende Events:
08.-11. November 2016: Besuchen Sie uns auf der electronica in München -> Halle B1 Stand 538
16. November 2016: Nachmittagsseminar mit unserem Partner Irlbacher zum Thema „Glas als innovatives Material für moderne HMI’s“
17. November 2016: Juristisches Seminar in Linz: Einsatz von Open Source-Software in der Industrie
06. Dezember 2016: Nachmittagsseminar mit unserem Partner sequality software engineering zum Thema Usability
>> Weitere Informationen zu diesen Veranstaltungen und Neuigkeiten aus der Elektronikbranche finden Sie auf www.ginzinger.com/techtalk
next reply other threads:[~2016-10-21 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 9:19 Henri Roosen [this message]
2016-10-21 10:55 ` commit-3ac72b7b63d5 breaks networking on iMX28 Fabio Estevam
2016-10-21 11:09 ` Henri Roosen
2016-10-21 13:39 ` Eric Nelson
2016-10-21 13:43 ` Fabio Estevam
2016-10-21 13:48 ` Eric Nelson
2016-10-21 13:46 ` Eric Nelson
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=bc6aa851-3f52-2274-47dc-4933662648a1@ginzinger.com \
--to=henri.roosen@ginzinger.com \
--cc=eric@nelint.com \
--cc=fugang.duan@nxp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.