00:52 <naobsd> github linux-rockchip is this community. rockchip-linux is rockchip. anyone can fork any repo freely...

01:05 <naobsd> about wiki, there are many errors in many pages, and there are outdated pages...

01:17 <naobsd> for rk3288, there are some incompatible systems,

01:19 <naobsd> 1. Android (proprietary bootloader + 3.10 kernel) and Linux images based on same bootloader/kernel

01:19 <naobsd> 2. Chromebook (dedicated bootloader + 3.14 kernel)

01:19 <naobsd> 3. mainline u-boot + mainline kernel

01:21 <naobsd> 4. Rockchip's Linux distro(?) (mainline-based u-boot + mainline(4.4)-based kernel)

01:23 <naobsd> (3. and 4. are very similar, but generally) they are different thing

01:25 <naobsd> only mask rom things are common

01:28 <naobsd> spl location is common too, but there are some spl implementations

01:43 <libv> naobsd: ok

01:43 <libv> so 1 and 3 are going to be the focus of the manual build howto

01:44 <naobsd> I think 1. should not be used anymore (for Linux system)

01:45 <libv> but perhaps 1 gets people a 100% working linux system whereas 3 only does 60%

01:45 <naobsd> some features missed in mainline (e.g. VPU) is supported in 4.

01:46 <libv> ok

01:46 <libv> 3 and 4 it is then

01:46 <libv> naobsd: this is what i am talking about, btw: http://linux-rockchip.info/mw/index.php?title=RK3288_Manual_build_howto

01:47 <libv> in time, individual sections get moved to their respective pages

01:47 <naobsd> http://rockchip.wikidot.com/ (by Rockchip) is basically for 4., but everything is very new,

01:47 <libv> this is what we were doing at sunxi

01:47 <libv> ok

01:48 <libv> also, loads of activity on the ml, but no useful documentation

01:49 <libv> why not go rub yourself one off instead

05:59 <stdint> phh, you would see the kernel driver has been release for a while

05:59 <stdint> but a few problems in kernel reminded

08:17 <PaowZ_> Hi there ! I'm currently working on modifying HDMI driver for adding a new resolution.. I modified rk_hdmi_lclc.c in order to add my new resolution but I can't see it once HDMI chip is up.. I know this sounds like silly question.. I'm not used to kernel build, therefore I don't where to get started to debug this.. any clue would greatly appreciated, thks :)

09:08 <phh> stdint: which repo should I follow to keep me updated on your changes? https://github.com/rockchip-linux/kernel/tree/vpu-service-4.4 & https://github.com/hizukiayaka/rockchip-video-driver/tree/v4l2_libvpu_fast ?

09:11 <stdint> phh, not VA-API

09:11 <phh> ok, so there is no repo to follow until it's published, ok

09:13 <stdint> PaowZ_, why do you do that, the resolution is decided by kms

09:13 <stdint> phh, and v4l2_libvpu_fast is for h264 and not ready yet

09:13 <stdint> currently I have no time in that

09:14 <phh> ok ok, I'll stop annoying you with that

09:14 <stdint> I am ok with that

09:15 <stdint> phh, I could offer you a binary version, but it won't work with most of hevc video

09:16 <stdint> I mean those 4K hevc video, 1080p seems fine

09:17 <phh> it my tests can be useful for you, then yes, else it sounds like it would be extra effort for you with no real upside

09:18 <phh> s/it/if/

09:18 <stdint> phh, if you could offer the test result and failure video it would help

09:18 <stdint> tell me you email address in private msg

09:18 <phh> right, then that's a deal :)

09:20 <phh> stdint: got it?

09:21 <stdint> yes

09:23 <stdint> got it?

09:26 <PaowZ_> stdint: I need an output of 1024x768p. This resolution is not present in the driver.

09:27 <PaowZ_> stdint: I therefore applied this "trick" http://wiki.radxa.com/Rock/Hdmi_Resolution

09:32 <stdint> ok, not a standard way, then I don't know

09:35 <phh> stdint: yup, thanks

09:36 <PaowZ_> HDMI discovery has been disabled looking at code.. you have to force it to a pre-defined resolution except the one I need is not present.