08:45 <ericbutters> hey.. anyone knows if there is a wayland image available for nitrogenboard?

12:24 <diego_r> ericbutters: I don't know of prebuilt images, but you should be able to build one using Yocto

12:25 <ericbutters> diego_r: okay thanks. btw, do you know where i can download vivante opengl (es) sdk?

12:29 <diego_r> ericbutters: you can try looking here, but don't know if there's any specific SDK. You can program regular OpenGL ES.

12:29 <diego_r> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=i.MX6Q&fpsp=1&tab=Design_Tools_Tab

14:53 <vpeter> Hi all.

14:53 <vpeter> Can someone give me advice? I would like to compile kernel 3.0.35 with gcc 4.9. But after running it it crash very early with Unable to handle kernel NULL pointer dereference at virtual address 00000001.

14:53 <vpeter> Full log http://pastebin.com/avEeAPcq If I use gcc 4.7 everything runs smoothly.

18:44 <aholler> vpeter: there are two older fixes for memset with gcc >=4.7 and one which was just discovered with 3.16

18:45 <aholler> look at the latest patchset for 3.2 to find the memset-fix

18:47 <aholler> but in general it isn't a very good idea to compile stone old kernels with brand new compilers

18:49 <aholler> same for u-boot.

18:51 <vpeter> Thank you. I will look around now that I know what to look for.

18:52 <vpeter> Can agree about mixing stone age with new age :) But doing some experiments...

18:52 <aholler> the one for 3.16 is from linus and even ended up in some news

18:52 <aholler> because news-people do like his flames ;)

18:53 <vpeter> Like Linus Torvalds: "GCC 4.9.0 Seems To Be Terminally Broken"

18:54 <aholler> yes, broken as most linux arm-kernels ;)

18:54 <vpeter> So it seems.

18:55 <vpeter> But who am I to judge.

18:56 <aholler> a victim ;)

18:58 <vpeter> At least I'm doing this for hobby.

19:49 <perul> dv_: I finally got a working kernel building environment and could test the wandboard patches, but unfortunately I still get the same mem allocator failures.

19:50 <perul> Here is the dmesg output again: http://pastebin.com/ejkP2RvM

20:41 <aholler> I had to disable dma in order to use brcm_patchram_plus, so there still might be some bug inside the dma-engine

20:44 <aholler> but it also might be a problem in the tty-subsystem (which still goes through some changes/bugfixes), so I haven't had a deeper look at it and prefered to go the easy route with disabling dma for the one uart