00:46 <bashintosh> hi all

00:51 <bashintosh> on firefly rk3288, are eDP timings read from the lcd-box.dtsi tree?

01:19 <naobsd> oh I missed some discussion here...

01:19 <naobsd> there is RK u-boot with (probably) rk3368 support in rk312x android 5.1 sdk http://git.us.linux-rockchip.org/?p=rk312x_android5.1_sdk.git;a=blob;f=u-boot/UserManual;h=b55f37f69353d55f3efb8062e9118ad88c7759f2;hb=refs/heads/firefly/fireprime

01:20 <naobsd> it's not rk3368 android sdk, but I guess RK shares some code with other SoCs

01:21 <naobsd> (I think there is no rk3368 SDK in public yet)

01:24 <naobsd> btw I tried to ask Tronsmart promotion, but I cannot get any reply...

02:11 <loongson> hello naobsd, hello cnxsoft! Both of you ROCK!!!

02:13 <loongson> Who's the best guy to ask about kernel 4.0 onto rk3288 boards(radxa rock2 square)?

02:14 <loongson> debian unstable has a linux 4.0 armmp kernel available, any way to just massage it with mkbootimg and flash it to the boot partition?

02:17 <loongson> Why is it that when the debian upgrade does its thing, it can't place the kernel into the emmc boot partition. All it does now is create a /boot directory and places it there, but never gets called by the real radxa rock2 square boot within the nand boot partition. Does that imply Debian's kernel install needs to be tweaked for rockchip specific mkbootimg stuff along with update_tool specific stuff to land the real kernel

02:17 <loongson> into the emmc boot partition? Is there a way to tell it to just boot off the main partition where the rest of linux is installed?

05:31 <bashintosh> Does anyone know if the RK3288 eDP TX supports enhanced framing? I went through most of the documentation I have available from Rockchip but couldn't find anything related.

07:15 <mmind00> maz: it looks like naobsd found the relevant parts for the trusted firmware stuff for rk3368: http://git.us.linux-rockchip.org/?p=rk312x_android5.1_sdk.git;a=blob;f=u-boot/tools/rk_tools/RKTRUST/RK3368TRUST.ini;h=dcff1ac07e85f61f8ac19364dcc8c9461d14e5e5;hb=refs/heads/firefly/fireprime - binaries in http://git.us.linux-rockchip.org/?p=rk312x_android5.1_sdk.git;a=tree;f=u-

07:15 <mmind00> boot/tools/rk_tools/bin/rk33;h=cda24cb3466881471230879aa01c374585420d93;hb=refs/heads/firefly/fireprime

07:21 <rperier> hi all

08:48 <cristian_c> apritzel: hello

09:10 <maz> mmind00: looks like I should clone this thing quickly then...

09:19 <apritzel> cristian_c: hi

09:24 <cristian_c> apritzel: I rebuilt the kernel, but I see in dmesg driver failed to load (for no ack issue). Anyway, I see also android dmesg says driver failed to load

09:24 <cristian_c> I mean wm831x pmic driver

09:25 <cristian_c> *android dmesg too

09:25 <cristian_c> sorry

09:25 <cristian_c> so, it seems wm831x is useless

09:26 <cristian_c> since devices work in android

09:27 <cristian_c> wm8326 is now located in /sys/bus/i2c/devices, i2c-1 at address 0x34, anyway, I see same error messages for cameras in my dmesg

09:29 <apritzel> cristian_c: you mean the no-ack error messages?

09:29 <cristian_c> apritzel: yeah, I don't see differences about that issue

09:29 <cristian_c> apritzel: but I've news about another issue :)

09:30 <apritzel> but you don't see no-ack messages with the Android kernel?

09:30 <cristian_c> apritzel: after flashed and booted, I saw internal display always blank

09:30 <cristian_c> apritzel: it seems not

09:31 <cristian_c> but same failed to probe wm831x in both android and ubuntu

09:31 <cristian_c> so I think wm831x is not related to issues

09:32 <cristian_c> apritzel: anyway, after booted, I've took a spotlight

09:32 <cristian_c> and I've targeted the display withthe spotlight

09:32 <cristian_c> taaaa-daaa!

09:33 <apritzel> no backlight?

09:33 <cristian_c> I've seen the login ubjntu screen in the display

09:33 <cristian_c> apritzel: yep

09:33 <apritzel> so display was working but just dark as hell?

09:33 <cristian_c> apritzel: yep

09:33 <cristian_c> issue is missing backlight

09:34 <apritzel> backlight is mostly controlled by some PWM drivers, good luck with that ;-)

09:34 <cristian_c> but it seems image is well rendered in the lcd display panel

09:34 <cristian_c> apritzel: :(

09:35 <apritzel> well, if you have a working (Android) kernel, you could look for mesages related to pwm or the like

09:35 <apritzel> and then try to find and enable that driver, also look in the device tree

10:04 <cristian_c> apritzel: thanks for the answer, I've read now

10:23 <cristian_c> apritzel: I've to check again, anyway I don't remember 'pwm' related messages in android :)

10:24 <cristian_c> apritzel: I looked at /sys/class/backlight in ubuntu and there is a directory called 'rk28_bl'

10:24 <cristian_c> my platform is rk30sdk

10:26 <cristian_c> rk28_bl is a link directory, anyway it contains the common files brightness, max_brightness, actual_brightness, bl_power, etc...

10:26 <apritzel> cristian_c: is that a phone or table?

10:26 <apritzel> tablet?

10:27 <cristian_c> actual_brightness = 126, brightness = 127, max_brightness = 255

10:27 <cristian_c> apritzel: tablet

10:27 <cristian_c> bl_power = 0

10:28 <apritzel> well, the pwm just _regulates_ the brightness, turning it on at all is still something different

10:28 <cristian_c> online documentation about backlight is not very helping for me, I've tried echo command to brighness file and bl_power. File values change but nothing happens

10:29 <cristian_c> apritzel: ah, ok, thanks fo the info :)

10:31 <cristian_c> I've tried also xbacklight command line tool, and it returns 'no outputs contain backlight property', arclinux wiki says to change xorg.conf line, but this file doesn't exist in my distro, so I've tried to create a new one from tty, but reconfigure xorg fails