16:49 <memleak> hi all, so if this channel is generally not the most active of all places for imx6 development, where is it?

16:49 <memleak> like where do all the imx6 kernel / uboot guys talk?

16:50 <memleak> i hope that the answer is not "mailing list"

16:52 <vpeter> You have channels for all the boards.

16:53 <memleak> vpeter, nice to see you again!

16:55 <vpeter> you too.

17:08 <jnettlet> memleak, it depends.

17:11 <angolini> what the problem with mailing list?

17:13 <jnettlet> no more mailing lists

17:21 <angolini> well, i'm not sure what "imx6 kernel/uboot guys" means, but probably they talk about the patches on the mailing list.....

17:21 <angolini> maybe, what in question here is the "talk"

17:33 <memleak> jnettlet, hey i remember you from coreboot! how you been?

17:36 <memleak> well there's not a whole lot of info i could find online in regards to compiling mainline uboot and kernel with imx6 boards, it's always 3.0 kernels from 3rd party github repos etc. secondly i can't find much information on how xf86-video-armada talks to kernel DRM if vivante_drv.c (kernel source file for GPU) is a stub / null

17:37 <memleak> i also saw a mesa tree from 10.4 for vivente, is that the latest one?

17:39 <memleak> just trying to find experienced imx6 devs who could help me sort out all the current git repos for vivente because the trees I found all need work except for russell king's armada driver, which i'd be more than happy to do if i knew exactly where the devs left off

17:40 <memleak> X is my thing, kernel eh, uboot.. that's me playing with fire

17:42 <memleak> I also remember you and I working on the openchrome drivers years ago

17:45 <memleak> with uh.. what's his name.. Thomas Hellstrom!

17:57 <angolini> regarding vivante, you can be a good boy, and use the kernel your board's vendor recommends. it means, 3.0 or 3.10 kernels

17:57 <angolini> or you can be a bad boy

17:58 <memleak> ah 3.10 has vivente code?

17:58 <memleak> (obv 3rd party but still)

17:58 <angolini> no, the kernel from your vendor has vivante code

17:58 <angolini> and only the open vivante code, of course

17:58 <jnettlet> memleak, good. still dabbling in coreboot. have more code that eventually needs to be upstreamed than I want to think about.

17:59 <jnettlet> well mainline u-boot is very board specific still. Even our boards have only started making it upstream due to other community developers efforts.

18:00 <jnettlet> rmk's armada driver needs the etnaviv patchset that he carries in a series of patchsets. We are trying to coordinate efforts but are waiting on some work from pengutronix.

18:00 <vpeter> angolini: I think memleak will be/is the vendor :)

18:00 <memleak> any glue in vivante_drm.c that's useful or just description info?

18:01 <memleak> where is that kernel tree i was looking at yesterday >_>

18:01 <jnettlet> vivante_drm is just a dummy stub to fool Xorg into using vivante/freescale's binaries

18:01 <memleak> its supposed to be a stub!?

18:01 <memleak> wait, binaries...

18:02 <jnettlet> if you are using a freescale based kernel tree then yes.

18:02 <angolini> so my default answer is "use kernel from freescale"....

18:02 <memleak> http://ftp.arm.linux.org.uk/cgit/xf86-video-armada.git

18:03 <jnettlet> yeah that uses etnaviv-drm, which exists but is in a highly developmental state

18:03 <memleak> ah now i'm getting somewhere! where is etnaviv-drm code?

18:03 <jnettlet> all over

18:03 <jnettlet> there is 1 set of patches posted to the drm-devel mailing list as an RFC

18:04 <memleak> current WIP tree that russell king is most likely using?

18:04 <jnettlet> there is another set here. http://www.home.arm.linux.org.uk/~rmk/cubox/hummingboard-cubox-i-v4.1-rc1-20150606/

18:04 <jnettlet> which is the latest work russell has done.

18:05 <jnettlet> I still have my patchset hanging out waiting to see what changes pengutronix makes to the kernel api

18:06 <memleak> thank you jnettlet you rock!

18:06 <memleak> still a cool guy after all these years!

18:07 <jnettlet> has it been that long?

18:07 <jnettlet> well thanks. I try my best

18:08 <angolini> i knew irc is a place for bad boys

18:10 <memleak> do you know if the DRM code in the hummingboard drm patch folder is generic or specific to only the hummingboard?

18:11 <memleak> i.e. no hard coded board specific stuff in there

18:11 <jnettlet> memleak, if you are using an upstream kernel then 4.1 is definitely your best starting point. Although there are still some missing patchsets spread around the mailing lists. If you want to use the mem2mem csi/mipi interfaces then you will need some patches form lucas over in the linux-media mailing list

18:12 <jnettlet> all of our upstream code...especially rmk's is as generic as can be.

18:12 <memleak> that's what i love to hear! woo!

18:12 <memleak> rmk is a badass, glad he's involved in the project too

18:13 <jnettlet> yeah. great guy and definitely elite

18:13 <memleak> very much so

18:13 <jnettlet> pengutronix has done a lot of upstream heavy lifting as well

18:15 <memleak> kudos to him working on it as well and anyone else! this is good news.

18:18 <memleak> so i've got most of the drm code in that folder, found the official armada driver, the only thing left is mesa. is this the latest 3D code: https://github.com/laanwj/mesa