From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: Alignment issues with freescale FEC driver Date: Fri, 23 Sep 2016 22:45:53 -0400 (EDT) Message-ID: <20160923.224553.1824171056324385383.davem@davemloft.net> References: <0fe7a310-2d2f-4fca-d698-85d66122d91c@nelint.com> <20160923181301.GD22965@lunn.ch> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: andrew@lunn.ch, edumazet@google.com, fugang.duan@nxp.com, otavio@ossystems.com.br, netdev@vger.kernel.org, troy.kisky@boundarydevices.com, rmk+kernel@arm.linux.org.uk, cjb.sw.nospam@gmail.com, linux-arm-kernel@lists.infradead.org To: eric@nelint.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:60758 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756764AbcIXCp7 (ORCPT ); Fri, 23 Sep 2016 22:45:59 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Eric Nelson Date: Fri, 23 Sep 2016 11:35:17 -0700 > From the i.MX6DQ reference manual, bit 7 of ENET_RACC says this: > > "RX FIFO Shift-16 > > When this field is set, the actual frame data starts at bit 16 of the first > word read from the RX FIFO aligning the Ethernet payload on a > 32-bit boundary." > > Same for the i.MX6UL. > > I'm not sure what it will take to use this, but it seems to be exactly > what we're looking for. +1 From mboxrd@z Thu Jan 1 00:00:00 1970 From: davem@davemloft.net (David Miller) Date: Fri, 23 Sep 2016 22:45:53 -0400 (EDT) Subject: Alignment issues with freescale FEC driver In-Reply-To: References: <0fe7a310-2d2f-4fca-d698-85d66122d91c@nelint.com> <20160923181301.GD22965@lunn.ch> Message-ID: <20160923.224553.1824171056324385383.davem@davemloft.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org From: Eric Nelson Date: Fri, 23 Sep 2016 11:35:17 -0700 > From the i.MX6DQ reference manual, bit 7 of ENET_RACC says this: > > "RX FIFO Shift-16 > > When this field is set, the actual frame data starts at bit 16 of the first > word read from the RX FIFO aligning the Ethernet payload on a > 32-bit boundary." > > Same for the i.MX6UL. > > I'm not sure what it will take to use this, but it seems to be exactly > what we're looking for. +1