09:05 <corkie> mmind00 hey, you around? do you still have your MX4V_V20 rk3229 board and or know of any bootable images for it?

09:12 <mmind00> corkie: my rk3229 still gathers dust, not having a working bootloader yet ... other projects somehow always got in the way

09:31 <corkie> mmind00: ah yeh projects all over the place heh, i was just about to play around with the tvbox again, i see kernel 4.4 support for rk322x at the rockchip wiki, and i see build.files over at the github for rk3229, and the board has that Mali400 gpu which seems to be much popular, i can flash android ROMs using TWRP, all these little things makes me hope there is something out there, or that i would be able to build

09:31 <corkie> my own, not sure what iam getting myself into here

09:31 <corkie> the rabbit hole is deep for sure

09:33 <mmind00> corkie: not thaaaat deep, I guess ... once you have a process on how to make it load your custom kernel, it shouldn't be that hard :-) ... for me that includes replacing the bootloader, but when it should "just work", you might be able to use the one already on the device

09:34 <mmind00> corkie: but I really don't use the vendor-specific processes nor their kernel, so you'll need to explore that rabbit hole yourself ;-)

09:36 <corkie> been a couple o years now but i saw this on my screen once, so i have some hope heh https://i.imgur.com/Pa5yZ9H.jpg

09:40 <corkie> hrm how woud you check if the bootloader needs to be replaced? just write random/generic 32bit arm mali gpu image to SDcard and try to boot it?

09:41 <mmind00> corkie: the rockchip fork of uboot should just work for the regular use-case of writing image stuff using Rockchip's process and tools

09:42 <mmind00> corkie: replacement would be necessary if you want to do fancy stuff, like using extlinux in uboot or netbooting (loading the kernel over the network)

09:50 <corkie> so build uboot with rk3229 "settings" and .dts .mk and whatnot files following the uboot guide at rock-chips wiki would be a good/bad place to start? heh iam sure i got some reading up on these things ahead of me

09:51 <corkie> it works fine for watching videos with the stock android image, but if i could use it as a pi-hole or tiny tiny server of some kind it would be awsumm

10:01 <corkie> pretty interesting stuff this kernel building is tho, i compiled my own some weeks ago, it boots in 2seconds! completely useless i guess but still fun to go thru the process

10:03 <corkie> maybe it will be easier to just mess up some android rom that still has networking going and play with that, mmm new projects <3

10:04 <corkie> well thanks for the reply there mmind00 , gave a lil bit more hope for the box hehe

11:50 <ezequielg> oh, marcodiego left.

13:28 <ezequielg> phh: the chromeos vpu driver supports VP8 encoding and decoding, H264 encoding and decoding, JPEG decoding, and VP9 decoding.

13:28 <ezequielg> sorry, JPEG encoding.

13:29 <ezequielg> phh: marcodiego, fwiw I will post MPEG-2 decoding patches soon. Thanks to Kwiboo who helped me.

13:29 <ezequielg> Also, the request API was not pushed by the cedrus people. It was pushed by the entire community, and cedrus became the first driver to use it.

13:30 <ezequielg> chromiumos kernel uses an old version of the request api.

13:31 <ezequielg> with the request API we will be able to support quite a few decoders and encoders.

13:31 <ezequielg> it's just that implementing and debugging takes time :-)

13:43 <ramcq> \o/