From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: Alignment issues with freescale FEC driver
Date: Fri, 23 Sep 2016 20:13:01 +0200 [thread overview]
Message-ID: <20160923181301.GD22965@lunn.ch> (raw)
In-Reply-To: <0fe7a310-2d2f-4fca-d698-85d66122d91c@nelint.com>
> Since the hardware requires longword alignment for its' DMA transfers,
> aligning the IP header will require a memcpy, right?
The vf610 FEC has an SHIFT16 bit in register ENETx_TACC, which inserts
two padding bits on transmit. ENETx_RACC has the same.
What about your hardware?
Andrew
next prev parent reply other threads:[~2016-09-23 18:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <troy.kisky@boundarydevices.com>
2016-09-23 16:43 ` Alignment issues with freescale FEC driver Eric Nelson
2016-09-23 16:54 ` Eric Dumazet
2016-09-23 17:19 ` Eric Nelson
2016-09-23 17:33 ` Eric Nelson
2016-09-23 18:13 ` Andrew Lunn [this message]
2016-09-23 18:30 ` Russell King - ARM Linux
2016-09-23 18:39 ` Eric Nelson
2016-09-23 18:35 ` Eric Nelson
2016-09-24 2:45 ` David Miller
2016-09-24 5:13 ` Andy Duan
2016-09-24 2:43 ` David Miller
2016-09-24 12:27 ` Eric Nelson
2016-09-23 17:37 ` Russell King - ARM Linux
2016-09-23 18:26 ` Eric Nelson
2016-09-23 18:37 ` Russell King - ARM Linux
2016-09-23 18:49 ` Eric Nelson
2016-09-23 20:22 ` Uwe Kleine-König
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=20160923181301.GD22965@lunn.ch \
--to=andrew@lunn.ch \
--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).