11:58 <Tenkawa> hi all.

11:58 <Tenkawa> I think this one should/hopefully will be easy to fix however asking for input.

11:59 <Tenkawa> compiled a 3.18 kernel for my xe303c12 and it definitely boots (can login and reset it with a init 6/reboot) however the console just blinked and did nothing as it booted up.

12:00 <Tenkawa> this feels framebuffer/setting related to me that I didnt compile in or I'm not passing in at boot.. any ideas?

12:01 <Tenkawa> or even possib;y a dtb tweak I need..

12:07 <Tenkawa> unfortunately I always find the odd ones

12:08 <sjoerd> 3.18 exynos defconfig didn't have the exynos DRM bits enabled

12:09 <Tenkawa> oh

12:09 <Tenkawa> Let me go check my config

12:09 <Tenkawa> sjoerd: do I need to pull in any src changes too?

12:10 <sjoerd> for snow, i always forget

12:10 <sjoerd> you'd have to ask javier__

12:10 <Tenkawa> ok. will do

12:11 <Tenkawa> thanks

12:12 <Tenkawa> so close...

12:12 <javier__> Tenkawa: you need the drm bridge patches from Ajay to have proper kms/drm support for Snow

12:12 <javier__> Tenkawa: if you just want a framebuffer then you can use nv-uboot with the simplefb driver

12:13 <Tenkawa> I tried nv-uboot with simplefb and was really striking out on the setup

12:14 <Tenkawa> I was probably overthinking it

12:15 <Tenkawa> I'll try that again here after this reboot

12:15 <Tenkawa> brb

12:17 <Tenkawa> ok

12:17 <javier__> Tenkawa: you just need to be sure that your nv-boot is the one with simplefb support (the one that fills the node in the FDT) and enable CONFIG_FB_SIMPLE in your kernel config

12:17 <Tenkawa> I just woke up so I'm at my best mentally.. time to try nv-uboot again

12:17 <Tenkawa> javier__: setting it up on the sd card nw

12:17 <Tenkawa> er now

12:18 <Tenkawa> ( I hope heehee)

12:18 <Tenkawa> do I need it to be a fb , boot, then root parts still?

12:18 <Tenkawa> with a env.txt

12:19 <javier__> sorry, I don't understand your question

12:20 <Tenkawa> the doc I have says to setup nv-uboot I need one part to dd the nv-boot to.. one partition to access /boot then one for root

12:20 <Tenkawa> that still applies right?

12:21 <Tenkawa> just wanted to make sure I hadnt missed anything recent

12:22 <Tenkawa> almost finished

12:26 <Tenkawa> ok theoreticly I'm ready to try ir

12:27 <Tenkawa> er it

12:27 <Tenkawa> I'll bbiaf

12:39 <Tenkawa> got a little closer

12:39 <Tenkawa> solid white screen on boot

12:39 <Tenkawa> can someone verify what LOADADDR I should build uimage with?

12:41 <Tenkawa> ahh just noticed a dtb change I hadnt copied over

12:41 <Tenkawa> oops

12:41 <Tenkawa> brb

13:08 <Tenkawa> hi all

13:08 <Tenkawa> is there any way to have nv-uboot not reboot on failed boot?

13:09 <Tenkawa> it appears to be mostly working but now it starts booting then immediately reboots

13:09 <Tenkawa> I think I'm passing a bad cmdline to the kernel however cant confirm because its lightning fast

13:11 <Tenkawa> got an idea... bbl heheheh

13:23 <Tenkawa> last message I got was failed to add board information in fdt

14:15 <dudas> hi

14:16 <dudas> i am having a cuestion with compile uboot

14:16 <dudas> to compile uboot in odroid u3

14:16 <dudas> does somebody help me ?

14:16 <dudas> sorry my language is spanish: can somebody help me, please

14:16 <dudas> english

14:17 <dudas> ld: error: /usr/lib/gcc/arm-linux-gnueabihf/4.9/libgcc.a(bpabi.o) uses VFP register arguments, u-boot does not ld: failed to merge target specific data of file /usr/lib/gcc/arm-linux-gnueabihf/4.9/libgcc.a(bpabi.o) ld: error: /usr/lib/gcc/arm-linux-gnueabihf/4.9/libgcc.a(_divdi3.o) uses VFP register arguments, u-boot does not ld: failed to merge target specific data of file /usr/lib/gcc/arm-linux-gnueabihf/4.9/libgcc.a(_divdi3.o)

14:17 <dudas> thanks

14:20 <dudas> i would like update uboot

14:20 <dudas> in odroid u3