[BUG]: imx6q (wandboard): Very unstable ethernet since kernel 3.16
George Joseph
george.joseph at fairview5.com
Fri Aug 8 17:41:57 PDT 2014
On Fri, Aug 8, 2014 at 6:33 PM, Troy Kisky
<troy.kisky at boundarydevices.com> wrote:
> On 8/8/2014 3:51 PM, George Joseph wrote:
>> On Fri, Aug 8, 2014 at 4:02 PM, Troy Kisky <troy.kisky at boundarydevices.com
>> <mailto:troy.kisky at boundarydevices.com>> wrote:
>>
>> On 8/8/2014 7:58 AM, Thomas Scheiblauer wrote:
>> >
>> >
>> > Indeed, commenting out these 2 lines in
>> > arch/arm/boot/dts/imx6qdl-wandboard.dtsi fixes my problem without having
>> > to increase TX_RING_SIZE.
>> > Thank you very much!
>> >
>> Could you also please checkout commit
>>
>> commit 9fc77821b17155c6e0ab50b1e1dd80c2b0e63e98
>> Author: Sascha Silbe <x-linux at infra-silbe.de <mailto:x-linux at infra-silbe.de>>
>> Date: Thu Feb 6 23:24:13 2014 +0100
>>
>> ARM: dts: imx6qdl-wandboard: use GPIO_6 for FEC interrupt
>>
>>
>> and see if it also shows ethernet instabilities?
>>
>>
>> I'm confused by the references to GPIO_6 and GPIO1_IO06 as it relates to the wandboard. According
>> to the schematic for both the rev B1 and C1, the GPIO_6 PAD is physically connected to pin 30 on the
>> camera interface and according to the dtb tree, GPIO1_IO06 isn't mapped to any PAD.
>>
>> This kinda fits with my own observation which is that Ethernet is working fine (40MB/s sustained)
>> regardless of whether fec is using "gpio1 6" and "intc 0 119" for extended interrupts or the default
>> "intc 0 118" and "intc 0 119". Otherwise stock 3.16.0 on WB Quad C1.
>>
> Are you using a wandboard also? With or without camera plugged in?
Wandboard Quad rev C1 with nothing connected to the camera connector.
I have 4 of them without problems.
>
>
> Same question for Thomas. Do you have a camera?
>
>
> Troy
More information about the linux-arm-kernel
mailing list