11:10 <mrjay> hi

11:11 <mrjay> anyone has any info when rk3399 devices will hit market ?

11:39 <stdint> mrjay, it would be soon

11:39 <stdint> maybe in the Q4 of 2016

11:40 <mrjay> stdint: this year soon or the next year soon ?

11:40 <mrjay> ok

11:40 <stdint> 2016

11:40 <mrjay> cool

11:41 <mrjay> i'll wait then

13:19 <busterbcook> howdy

13:20 <busterbcook> before I go down a wrong path too deeply, has anyone attempted building a non-verified uboot for rockchip chromeos devices?

14:46 <ayaka> busterbcook, it may not work

14:57 <busterbcook> ok ayaka, I've built an image, looking at how to wrap it with the kernel tools for the veyron boards. will let you know how it goes.

14:59 <ayaka> busterbcook, I am not familiar with chrome book, but I know the chrome woul verified the checksum in most devices

14:59 <busterbcook> yah, I have that bit disabled for now, or can possibly sign with a dev key if needed

15:03 <busterbcook> something like this might work, trying it now: http://linux-exynos.org/wiki/ARM_Chromebook/Building_u-boot

17:51 <busterbcook> well, I can build an image that loads now, and gets a black screen - I'd call it progress :)

23:16 <naobsd> hmmm