17:54 <rory096> alright back to this cx-929... it's been a while

18:23 <popolon> https://www.youtube.com/watch?v=BQ4_C9f_D08

18:23 <popolon> blender on RK3288 :)

18:23 <popolon> still no neon optimization, no hw acceleration, but works nicely bor basic scenes

18:24 <popolon> s/bor/for

18:28 <amstan> popolon: that's pretty cool

18:41 <popolon> :)

18:42 <popolon> there are some GLES options, didn't managed to use them, even (at least some) blender coders don't know if this even worked)

18:43 <popolon> looking at how to make it working, I seen other SIMD than Neon for ARM

18:44 <popolon> don't know if that's a new feature of 64bits arm or for some specific hw

18:50 <popolon> WMMX

18:50 <popolon> or IWMMXT

18:51 <popolon> https://gcc.gnu.org/onlinedocs/gcc/ARM-iWMMXt-Built-in-Functions.html

18:54 <popolon> looks like this is used on marvell familly (so derivated from intel)

20:40 <rory096> cros_workon info --board=$B sys-kernel/chromeos-kernel-3_14

20:40 <rory096> sys-kernel/chromeos-kernel-3_14 chromiumos/third_party/kernel src/third_party/kernel/v3.8

20:40 <rory096> what's up with that? can i change it to /kernel/v3.14?

21:20 <rory096> *shrug* guess i'll just try using 3.8

21:21 <rory096> wow, i actually managed to compile a kernel

21:24 <cristian_c> congrats!

21:52 <rory096> thanks!

21:53 <rory096> now just to compile this device tree

21:54 <rory096> anyone know where 'make ARCH=arm dtbs' should output? the internet says it's in /arch/arm/boot/dts - the same as the dts files - but nothing shows up there even though make seems to be doing work

21:56 <amstan> rory096: woo, more people working on chromebooks

21:57 <amstan> rory096: excuse me for being lazy, but i generally like refering people to the archlinuxarm pkgbuild, just because it's pretty simplistic looking: https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-veyron/PKGBUILD

21:57 <rory096> more of a chromebit, really. it's this little guy: http://androidtvbox.eu/cx-929-tv-stick-with-external-wifi-antenna-powered-by-rk3288/

21:57 <amstan> ah, too impatient for the real thing? lol

21:58 <amstan> rory096: i see lots of arch/arm/boot/dts/ in https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-veyron/kernel.its

21:59 <rory096> amstan: so will that build a whole image for me? will it let me use a custom dts?

21:59 <amstan> hold on, are you trying to compile chromeos for it?

21:59 <rory096> yep too impatient... and don't want to drop $100 each

21:59 <rory096> yeah, chromiumos

21:59 <amstan> ok, ignore everything then

21:59 <rory096> haha fair enough

22:00 <amstan> emerge-veyron_$whatever chromeos-kernel-3_14 generally does it's business(in terms of build files) in a different location

22:01 <amstan> rory096: perhaps /build/veyron_$whatever/tmp/portage/sys-kernel/chromeos-kernel-3_14-9999/

22:02 <amstan> you'll have to convince the emerge to give you the dtbs, it generally likes just making a kernel partition(since that's all chromebooks take)

22:03 <rory096> hmm

22:03 <rory096> looks like everything in my /tmp/portage is from the kernel build earlier, but not the dtb compile

22:03 <rory096> (i'm trying to concatenate the dtb to my zImage)

22:12 <rory096> hmm, /build/veyron/tmp/portage/sys-kernel/chromeos-kernel-3_14-3.14-r1213/work/chromeos-kernel-3_14-3.14/scripts has this Makefile.dtbinst that says "installs all dtb files listed in $(dtb-y) either in the INSTALL_DTBS_PATH dir or the default location: $INSTALL_PATH/dtbs/$KERNELRELEASE"

22:12 <rory096> can't find any folders called dtbs though

22:13 <rory096> also, i'm a little confused why there's no 3_8 folders in there, only 3.14s

22:17 <rory096> could i maybe compile this .dtb outside of chroot? that should be platform agnostic, right?

22:20 <rory096> hmm no, can't access the arm gcc compiler

22:22 <rory096> bashintosh: did you ever manage to concatenate to a zImage?

22:36 <amstan> rory096: is this a fit image you want?

22:37 <amstan> rory096: i can get a tftp capable image from /build/${BOARD}/boot/vmlinuz

22:50 <rory096> amstan: yes, i think so. basically i'm trying to load an image onto the device with a custom device tree attached

22:50 <rory096> my boot/ is empty except for a 'boot-A.scr.uimg' and a 'boot-B.scr.uimg'

22:55 <rory096> though now that the kernel's compiled, don't I just need to flatten out the device tree into a .dtb and append it to the image file?

22:57 <rory096> maybe i should back up... is that the best strategy to port to this board?

23:05 <amstan> rory096: if you ran emerge, this was already done

23:07 <rory096> i never ran it explicitly, isn't that part of the kernel make?

23:07 <rory096> (how does it know which dts to use?)

23:07 <amstan> based on the its file

23:08 <amstan> rory096: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/master/eclass/cros-kernel2.eclass

23:08 <amstan> rory096: all of that happens when you run emerge

23:08 <amstan> including compiling dtbs, generating an its and so on

23:16 <rory096> hmm. so if the its is auto-generated, how can i manually specify which dts to use?

23:17 <rory096> or wait, it's installing all of them?

23:18 <rory096> "For boards where the device tree .dtb file is stored under /boot/dts, loaded into memory, and then passed on the 'bootm' command line, make sure they're all installed. We install more .dtb files than we need, but it's less work than a hard-coded list that gets out of date."

23:24 <rory096> but if that's true, how does uboot know which one to use?

23:25 <amstan> depthcharge generally knew the board name, and did a match on the ones available, not sure what uboot does

23:28 <rory096> see that's strange too, because the veyron overlay doesn't seem to really mention rk3288 anywhere

23:29 <rory096> except for /chromeos-base/chromeos-bsp-veyron/files/99-rk3288-gpio-charger.rules and 99-rk3288-ehci-persist.rules

23:30 <rory096> hmm i guess there's USE="${USE} rk32..." in the overlay's make.conf. also a kernel-3_14 there, which explains a bit