2016-03-27 09:23:53	@kido	hi MistahDarcy
2016-03-27 16:16:45	locusf	kido: hi
2016-03-27 16:17:00	locusf	I didn't add board name to the mkbootimg command line
2016-03-27 16:18:00	@kido	hi :) on some devices (like sw3) it is not needed
2016-03-27 16:20:25	locusf	okay
2016-03-27 16:40:54	@kido	have you tried asteroid's check-config yet? were you able to unpack and repack the android's boot.img with your config and were you able to boot android with a bitbakef default kernel?
2016-03-27 16:44:25	locusf	yes
2016-03-27 16:44:29	locusf	I could
2016-03-27 16:44:37	locusf	but I can't boot with the default kernel
2016-03-27 18:37:17	@kido	there seems to be something wrong with the kernel that is published on aosp then
2016-03-27 18:37:54	locusf	well that one doesn't even compile
2016-03-27 18:38:41	@kido	what do you use then?
2016-03-27 18:38:49	locusf	the one from asus website
2016-03-27 18:39:42	@kido	ok
2016-03-27 18:45:24	@kido	and that kernel with default athias defconfig gives you a zImage that doesn't boot when put together with the android's ramdisk? and if you repack a boot.img with the same settings but with the android's prebuilt kernel and ramdisk it works? You might want to try something like this: http://forum.xda-developers.com/zenwatch/development/tinykernel-t3169754
2016-03-27 18:46:01	@kido	If it also fails I can try to fix the compilation errors from aosp by myself
2016-03-27 18:48:40	locusf	it doesn't work on either
2016-03-27 18:49:02	locusf	on both above
2016-03-27 19:11:45	@kido	ah then it must be your mkbootimg config. where did you get it from?