13:27 <jurislav> hello

13:28 <jurislav> anyone tried to run linux on egreat u8?

13:28 <jurislav> RK3188

14:37 <tlwoerner> i'm curious to know more about the https://github.com/TeeFirefly repository: is this official or community?

19:03 <cristian_c> hi, I'd like to solve two issues with rk3188

19:05 <cristian_c> 1) I'd like to enable bt properly in ap6210

19:05 <cristian_c> I've found some strange behaviours, if I type rfkill list, I can see ap6210 bt interface in the output. I can block/unblock the software switch. Some months ago, I tried the patchram plus method but it's difficult to say why it doesn't work. So, I'd like to know if there is a method to set it properly either how I can collect useful info from commands/files. Any ideas?

19:07 <cristian_c> 2) I'd like to access to mount user readable/writable nand partition (i.e. /sdcard)

19:07 <cristian_c> I think loop* block files are related to mtd partitions and I think I could mount /system or /sdcard , mtdblock8 and mtdblock9, respectively (they are ext4 the first one and vfat the second one). So, I'd like to know if maybe I've to enable some CONFIG options in the kernel configuration file or to something else. Any ideas?

20:08 <rperier> did you enable something in /etc/X11/xorg.conf for armsoc ?

20:08 <amstan> rperier: omg! yes, i need that too

20:08 <amstan> can't get it running

20:08 <rperier> I would say yes because other it is not loaded at all

20:09 <amstan> using mmind's rockchip armsoc?

20:09 <rperier> it does not work at all in arch for me

20:09 <amstan> nope, me neither

20:09 <rperier> I tried with armsoc-chromium and with armsoc-rockchip

20:09 <rperier> both don't work

20:09 <rperier> no screen found

20:09 <amstan> armsoc-chromium won't work anyway, that's compiled for exynos

20:10 <rperier> yes this is what I did read in Xorg.log.0

20:10 <rperier> then I switched to -rockchip

20:10 <amstan> mmind00: any ideas for us poor folk trying to get it going?

20:11 <amstan> rperier, i assume yours looks similar: https://bpaste.net/show/eb7d563d0e7f

20:12 <rperier> don't compute something... which drm is in linux-veyron (aka chromeos kernel)

20:12 <rperier> ?

20:12 <rperier> mali drm... right?

20:12 <amstan> i'm not sure

20:12 <amstan> i think so

20:16 <cristian_c> anyway, some questions about rk3066

20:17 <cristian_c> I've enabled i2c debug in kernel configuration

20:19 <cristian_c> but I don't see newer error messages in log as previously

20:20 <cristian_c> I've not found info why i2c devices are not loaded

20:20 <amstan> cristian_c: sounds like a race condition which works better when you have more printf's because of timing

20:22 <rperier> amstan: nop, opening DRM does not work for me :D

20:23 <rperier> let's me retry

20:23 <cristian_c> amstan: so, how can I investigate better?

20:23 <amstan> cristian_c: not sure

20:24 <cristian_c> amstan: I've read dmesg and syslog ,many times

20:24 <cristian_c> I've tried also to increas sdram frequency

20:25 <cristian_c> from 300 to 360 MHz

20:25 <amstan> rperier: leming's not sure either

20:25 <amstan> rperier: i was hoping i could catch mmind

20:28 <rperier> wait... it was just a permission issue... it works like a charm in root

20:28 <rperier> at least xserver starts

20:28 <rperier> with armsoc

20:28 <amstan> rperier: how are you starting it as root?

20:29 <rperier> I was starting it as user , but just to check something (the permission issue) I started it as root yes

20:29 <rperier> via startx

20:29 <rperier> (that's easier to debug and see logs)

20:29 <amstan> sudo su, then startx?

20:29 <rperier> yep

20:30 <cristian_c> another question

20:31 <rperier> amstan: which xorg.conf do you use ? (I mean, do you activate armsoc explicitly ?)

20:31 <cristian_c> should I enable rfkill in kernel configuration for 3.0.8+ and rk3066?

20:32 <rperier> and... it does not work anymore... :/ (it seems to work randomly...)

20:32 <amstan> rperier: i tried the bare minimum: https://github.com/mmind/xf86-video-armsoc/blob/packaging/debian/debian/armsoc.conf

20:32 <cristian_c> currently, I can't lauch the command in terminal

20:33 <rperier> I will try the same one, just in case

20:40 <rperier> nop, Permission denied

20:40 <cristian_c> amstan: ok, I've found an interesting thing

20:41 <cristian_c> https://patchwork.ozlabs.org/patch/383191/

20:41 <cristian_c> amstan: in my log, I see many many many xfer messages related to i2c

20:42 <cristian_c> after I've enabled i2c debug

23:15 <mmind00> rperier: amstan: can you check if you have commit d3007dabeff4 ("drm/rockchip: register all connectors after bind") in your kernels?

23:16 <mmind00> this is in mainline since january and my addition to the commit message says " This patch is necessary to make X11 see screens it seems."

23:17 <amstan> mmind00: we both use the chromeos kernel

23:17 <amstan> hmm, neat, perhaps that's why

23:17 <amstan> i wasn't going crazy then?

23:18 <mmind00> amstan: hmm that would be strange then, because this is a change from Dan and I think I got it from the chromeos-kernel initially

23:45 <leming> that commit is in chromeos-3.14

23:51 <mmind00> leming: you could of course try my somewhat-stable branch :-) [https://github.com/mmind/linux-rockchip/tree/devel/somewhat-stable] with the rk3288_veyron_defconfig in there and see if this changes anything

23:53 <mmind00> at least on my debian it brings me a working x11 with xserver-xorg both in versions 1.16 and 1.17

23:53 <leming> comments from earlier today show it to be some permissions problem, i'm sure that can be found

23:53 <mmind00> ok ... I didn't read all of the backlog, so probably missed that

23:54 <leming> are you changing permissions on any devices other than mali?