On 11/10/2014 05:06 AM, Uwe Kleine-König wrote: > Hello Ezequiel, > > On Sun, Nov 09, 2014 at 11:56:14AM -0300, Ezequiel Garcia wrote: >> Very delayed third round of the support for the network controller present >> on Marvell Armada 370/XP SoC. >> >> The first patch enables the peripherals in a PUP register, which is required >> on RGMII ports. >> >> The second and third patches add support for Marvell's 88E1543 and 88E1545 PHY >> chips. >> >> The fourth patch adds the mvneta driver. Most of the configuration part is >> based on Linux's mvneta driver, while some of code organization is based >> on Barebox's orion-gbe driver. > I tested this series on top of 784b352aeeed with a patch to support my > ReadyNAS 104 (by Netgear, Armada 370 system, currently only second stage > booting from U-Boot, similar to mirabox with > armada-370-netgear-rn104.dts from next-20141106). > > Marvell>> tftp start_netgear_rn104.pblx > Using egiga1 device > TFTP from server 192.168.77.157; our IP address is 192.168.77.133 > Filename 'start_netgear_rn104.pblx'. > Load address: 0x2000000 > Loading: #################### > done > Bytes transferred = 292148 (47534 hex) > Marvell>> go 0x2000000 > ## Starting application at 0x02000000 ... > > > barebox 2014.11.0-00123-g422a0a9d46a8 #3 Sun Nov 9 21:35:11 CET 2014 > > > Board: NETGEAR ReadyNAS 104 > SoC: Marvell 6710 rev 1 > mdio_bus: miibus0: probed > eth1: got preset MAC address: 28:c6:8e:36:df:57 > of_get_named_gpio_flags: unable to get gpio num of device pca95540: -19 > of_get_named_gpio_flags: unable to get gpio num of device pca95540: -19 > of_get_named_gpio_flags: unable to get gpio num of device pca95540: -19 > of_get_named_gpio_flags: unable to get gpio num of device pca95540: -19 > malloc space: 0x01f00000 -> 0x03dfffff (size 31 MiB) > environment load /dev/env0: No such file or directory > Maybe you have to create the partition. > no valid environment found on /dev/env0. Using default environment > running /env/bin/init... > /env/bin/init not found > barebox:/ ethact eth1 > barebox:/ dhcp > eth1: 1000Mbps full duplex link detected > T T T T T T T T T T T T T T T T T T T T dhcp failed: Connection timed out > dhcp: Connection timed out > barebox:/ eth1.ipaddr=192.168.77.133 > barebox:/ eth1.netmask=255.255.255.0 > barebox:/ echo $eth1.ethaddr > 28:c6:8e:36:df:57 > barebox:/ ping 192.168.77.157 > T T T T T ping failed: Connection timed out > barebox:/ > > tcpdump on 192.168.77.157 (which is connected via a switch) worked just > fine from U-Boot, after all it served the barebox image. > > The pca9554 i2c device is only used for leds, so I don't think the error > messages above are related. > > Yesterday I saw a different error, that I cannot reproduce now with the > same barebox image. IIRC I first played around a bit with eth0 until > noticing that I need eth1. I didn't save the full log, but it resulted > in: > > barebox:/ ethact eth1 > barebox:/ dhcp > eth1: 1000Mbps full duplex link detected > eth1: transmit error 3 > dhcp failed: I/O error > dhcp: I/O error > > Any ideas? I can try to use a dtb without pinmux definitions later > today. > Hm, not really. I've tested this with my Armada 370 Mirabox and Armada XP Openblocks AX3-4 boards (I use kwboot to load the barebox image, so I don't jump from U-Boot). I guess we must be missing some config. What's confusing is that the Mirabox and the RN104 should be pretty similar in this regard (e.g. they use the same phy mode). Sebastian, do you have any ideas? -- Ezequiel García, Free Electrons Embedded Linux, Kernel and Android Engineering http://free-electrons.com _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
