03:55 <pnill> welp finally hit a wall in my journey, [ 11.763] no nand found !

03:55 <pnill> apparently this code is produced by a sunxi compiled lib with source I don't have.

03:55 <pnill> so I can't see what dtb config or etc it's referencing that could be failing

05:00 <pnill> [ 12.137]nand not support! channel 0 chip 0: ef f1 00 95 00 00 00 00

05:00 <pnill> so that's fun to find.

05:36 <pnill> Anyone know if I just replace an existing nand config in the nand table of the lib with the info from that one from another u-boot that has it statically compiled in

05:36 <pnill> if it'll work or if I'd expect to see some code differences as well to support an additional nand and not just config changes?

05:42 <pnill> BSP really sucks to deal with, why the hell do they do weird stuff like embed data in the headers of bins and such.

05:52 <pnill> nvm, got past that part.

08:51 <gamiee> I wonder who's nickname on sunxi wiki is "Alldinner" :D :D

08:53 <aperezdc> haha, great nickname

19:42 <wart_> hi folks. thanks for getting the wake-on-wifi (WOWLAN) stuff working. I've been playing around with it for a bit, and I had a couple questions. Hopefully I can get pointed in the right direction.

19:44 <wart_> The biggest question I have is that the kernel seems to have set CONFIG_WAKEUP_TYPE = 0xf which appears to cause the pinephone to wake up quite often.

19:44 <wart_> Peetz0r's original patch had it set to 0xd which seems a little better (disabling unicast).

19:45 <wart_> Anyway, I wondered if there was a way via the iw interface to adjust this (other than a recompile of the kernel)?

19:46 <wart_> or via iwpriv. Reference is here: https://gist.github.com/Peetz0r/bf8fd93a60962b4afcf2daeb4305da40

19:46 <wart_> Thanks in advance.

19:50 <wart_> Personally, I'd like to have it only wake up on 0x21 and 0x23 (magic packet and pattern match respectively).

20:02 <anarsoul> mripard: yann-kaelig: yann-kaelig's issue isn't lima issue, it's generic stability issue with the board

20:03 <anarsoul> lima works fine on A20, e.g. on cubieboard2

20:03 <anarsoul> but it fails badly with unexplicable errors even with simplest workloads like kmscube on cubietruck

20:03 <yann-kaelig> Hello. I can confirm, I have both of the boards cubieboard2 and cubietruck, only on cubietruck the issue occur where on cubieboard2 it works as expected

20:37 <yann-kaelig> How can I get all the clocks value on the linux 3.4.61 ? There is no such file like /sys/kernel/debug/clk/clk_summary and /sys/kernel/debug/clk directory, DEBUG_FS is set and mounted

20:38 <yann-kaelig> It's an old Ubuntu/Linaro distro with kernel 3.4.61 installed on the Nand of my cubietruck

21:48 <pnill> Anyone here evert dealt with the nand stuff before? I've hit a wall and don't really know where to go/what the problem is at this point

21:49 <pnill> [ 12.171]can't find uboot head

21:49 <pnill> [ 12.171]search nand structure: find a good block: 12, but no physic arch info.

21:49 <pnill> the normal firmware when booting u-boot doesn't throw those two things, and I'm not sure what it's expecting or if the nand on the board is bad or timing is bad or what.

21:50 <pnill> it does move past that but eventually goes into

21:50 <pnill> [ 12.735][NE]boot but not data!

21:50 <pnill> [ 12.743][NE]boot not find mbr table!!!!

21:50 <pnill> until it eventually fails and halts the boot process as aresult

21:50 <pnill> *a result