Date: Wed, 24 Nov 2010 15:05:44 +0700 From: mr armvn <mr.armvn@gmail.com> To: Milan Obuch <freebsd-arm@dino.sk> Cc: freebsd-arm@freebsd.org Subject: 2 ethernet interfaces with marvell chip 88F6281(kernel configure file DB-88F6XXX) Message-ID: <AANLkTi=x5K2gfY-=io6jWneOitZymMM5FgHV0U8c27Gn@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi Milan Obuch, I using DB-88F6XXX (http://wiki.freebsd.org/FreeBSDMarvell) to make image for our board, it's working but only one mge0 ethernet interface, I read some document about mge1 interface ( http://old.nabble.com/Marvell-Kirkwood-6281-mge1-interface-td26193068.html) but didn't success, can you help me give some right comment. My environment # uname -a FreeBSD 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 UTC 2010 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 Thanks On Thu, Oct 28, 2010 at 3:59 AM, Milan Obuch <freebsd-arm@dino.sk> wrote: > On Wednesday 27 October 2010 18:44:23 Rafal Jaworowski wrote: > > On 2010-10-27, at 16:56, Milan Obuch wrote: > > > On Tuesday 26 October 2010 23:19:59 Kristof Provost wrote: > > [snip] > > > >> In any case, what I wanted to see is already printed in the boot log. > > >> Both mge interfaces are using the correct memory locatins (0xf1076000 > > >> for mge1) and the correct PHY numbers. > > >> > > >> Did you statically configure the mac addresses in the DTS for this > boot? > > > > > > Yes. Without that, ether addres did not initialize and needs to be set > > > manually. > > > > > > However, after looking over older mails again and trying to look at it > > > from the other side, I found the reason. I am going to write a > follow-up > > > explaining the whole issue and how succesfully solved the problem... > > > please wait a bit, something unrelated needs to be done now... > > > > Have you got your MPP settings sorted out correctly? The second GE unit > > connections are multiplexed with other functions of the SOC and won't > work > > without proper set-up, see the hardware spec and the description of MPP > > bindings in the DTS sys/boot/fdt/dts/bindings-mpp.txt > > > > Exactly this was the reason, however file you mentioned was not that > helpfull > for me... but looking at dts for OpenRD client and hardware spec for > 88F6281 I > got the idea and after looking a bit at linux sources for guruplug server I > modified my dts and this also explain why frames could be received before > and > not sent - all pins set as gpio are inputs in a way, thus reading worked, > but > controller output was not connected to phy, so in effect tcpdump saw input > and > frames to be sent, but tha's on chip, and they did not get out of chip. > > That's it for theory, and now some summary - I am attaching patches I used > for > Guruplug to work, collected from older mails. Patch for mvwin.h and > ehci_mv.c > are necessary for USB to work correctly. I mentioned them in my first mail > dated October 20, 2010, original source is mail from Johny Mattsson dated > September 18, 2010. Patch for if_mge.c makes it unnecessary to specify phy > handle in dts and probes them automatically, originally in mail from > Norikatsu > Shigemura dated June 20, 2010. I modified it a bit to account for changes > in > sources in between. > > For kernel config see my first mail. New dts is attached here. > > One issue still remains - mge1 has no unique ether address, all-zero is set > upon reboot unless explicitly set in dts. This is small issue for me, need > not > be resolved urgently. > > A bit more important problem is gpio - I have line > > gpio0: <Marvell Integrated GPIO Controller> mem 0xf1010100-0xf101011f irq > 35,36,37,38,39,40,41 on simplebus0 > > in boot log/dmesg output, yet there is no /dev/gpio file of similar usable > with gpioctl. Some LEDs are connected to gpio pins, some pins are > accessible > through u-snap connector and thus are interesting for I/O... Any hint here? > > Regards, > Milan > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=x5K2gfY-=io6jWneOitZymMM5FgHV0U8c27Gn>