13:25 <afaerber> mmind00: ping

16:26 <sjg1> naobsd: I imagine that the boot ROM sets it up for emmc boot, so yes

19:47 <mmind00> afaerber: pong

19:48 <afaerber> mmind00: I was wondering whether you have further comments on my GeekBox patches, but by now I've prepared a v4 squashing some of them myself

19:48 <afaerber> mmind00: are you aware of any issues around GMAC? it seems to be broken now, not having made any changes

19:50 <mmind00> afaerber: except the comments on the lists, I didn't spot any issues ... kernelci is using the gmac for all their booting, so it should be spotted if the network is stopping to work

19:50 <afaerber> mmind00: it's not finding the PHY

19:50 <afaerber> I've put the error message into the cover letter

19:50 <mmind00> is the correct phy driver being build? :-)

19:51 <afaerber> I only did a linux-next rebase and did not unselect PHY drivers manually

19:55 <afaerber> s/v4/v3/

19:56 <mmind00> afaerber: strange ... at least on march 4th it was the rock2 was still finding its network: https://kernelci.org/boot/rk3288-rock2-square/job/next/kernel/next-20160304/defconfig/multi_v7_defconfig/lab/lab-collabora/?_id=56d975ef59b514481fa39b27

19:57 <afaerber> mmind00: maybe an rgmii vs. some rmii interface issue? took me a while to figure out the ext_gmac clock for v2 for lack of examples

19:59 <mmind00> afaerber: just to be sure, vcc_lan is defined and connected to the phy?

19:59 <afaerber> mmind00: unchanged since v2

20:01 <mmind00> afaerber: which linux-next is it you rebased on? There seems to be a lot of activity 4 days ago, that might be the source? [http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/drivers/net/ethernet/stmicro]

20:02 <afaerber> mmind00: I indicated the tag in the mail

20:02 <afaerber> next-20160304

20:02 <afaerber> which was the latest earlier today

20:03 <afaerber> and still is

20:04 <afaerber> mmind00: anyway, making some progress on the patches is more important to me than the current breakage

23:20 <naobsd> afaerber: gmac is working on my Orion R68G with next-20160302

23:21 <naobsd> afaerber: here is my patch and dmesg http://dl.linux-rockchip.org/rockchip/arm64/

23:22 <afaerber> naobsd: what about the latest next?

23:22 <naobsd> sorry, no time

23:22 <naobsd> afaerber: please add snps,reset-* props in gmac

23:22 <naobsd> it's for phy reset

23:23 <afaerber> naobsd: but where do I get the values from? didn't see them in original .dts

23:23 <afaerber> and I didn't need them before

23:24 <naobsd> well phy reset pin is not connected to any gpio on geekbox?

23:26 <naobsd> sorry I have to go out very soon

23:28 <afaerber> PHY_RST is connected to VCC_LAN but not to any GPIO as far as I can see

23:36 <naobsd> afaerber: ah I see... is phy not working even if it's on cold start?

23:37 <naobsd> afaerber: what happen if you remove always-on from vcc_lan?

23:38 <naobsd> some delay might be required after power on

23:39 <naobsd> or, I'm not sure, power on/reset need to be done after clock etc are prepared...?

23:39 <naobsd> I cannot remember detail

23:39 <naobsd> and have to go now

23:39 <naobsd> later

23:41 <afaerber> nope, cold boot makes no difference

23:42 <afaerber> gotta sleep now, bye