#linux-rockchip on 2014-11-21 — irc logs at freenode.irclog.whitequark.org

2014-10-07 12:46 ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip

00:15 <amstan> mmind00_: can you please also take a look at https://chromium-review.googlesource.com/#/c/227240/ ?

00:17 <mmind00_> amstan: I should've continued playing dead and not post the gerrit comment ;-) ... anyway 1:20am here, so I'll do that after sleeping if that's ok with you

00:17 <amstan> mmind00_: no problem, sorry, lol

00:17 <amstan> but you're right, it was because of that comment

00:17 <amstan> heheh

00:18 <mmind00_> amstan: :-D ... great, so gn8 for now ... at some point in the future I should also again aim for more regular sleep times

00:20 <naobsd> do you want to develop PX2 board anyone? I'll ask chipspark today, this will be last Q...

00:20 <naobsd> (I compared RK3066 and PX2 kernel/u-boot, basically both are same, no new thing for software developer)

00:22 <naobsd> probably only PX2 TRM is useful for most developers ;)

00:28 RayFlower has quit [Read error: Connection reset by peer]

00:29 RayFlower has joined #linux-rockchip

00:37 levd has joined #linux-rockchip

00:41 RayFlower has quit [Read error: Connection reset by peer]

00:42 RayFlower has joined #linux-rockchip

00:46 RayFlower has quit [Read error: Connection reset by peer]

00:47 RayFlower has joined #linux-rockchip

00:53 RayFlower has quit [Read error: Connection reset by peer]

00:54 RayFlower has joined #linux-rockchip

01:13 RayFlower has quit [Read error: Connection reset by peer]

01:14 RayFlower has joined #linux-rockchip

01:18 RayFlower has quit [Read error: Connection reset by peer]

01:19 RayFlower has joined #linux-rockchip

01:21 levd has quit [Remote host closed the connection]

01:22 levd has joined #linux-rockchip

01:43 levd1 has joined #linux-rockchip

01:44 levd has quit [Ping timeout: 240 seconds]

02:02 cnxsoft has joined #linux-rockchip

02:11 RayFlower has quit [Read error: Connection reset by peer]

02:11 RayFlower has joined #linux-rockchip

02:18 levd has joined #linux-rockchip

02:20 levd1 has quit [Ping timeout: 255 seconds]

02:26 RayFlower has quit [Read error: Connection reset by peer]

02:27 RayFlower has joined #linux-rockchip

02:29 RayFlower has quit [Read error: Connection reset by peer]

02:31 RayFlower has joined #linux-rockchip

02:32 levd has quit [Remote host closed the connection]

02:33 levd has joined #linux-rockchip

02:53 naobsd has quit [Quit: Page closed]

02:56 levd1 has joined #linux-rockchip

02:59 levd has quit [Ping timeout: 264 seconds]

03:16 RayFlower has quit [Read error: Connection reset by peer]

03:17 RayFlower has joined #linux-rockchip

03:21 levd has joined #linux-rockchip

03:23 levd1 has quit [Ping timeout: 255 seconds]

03:36 RayFlower has quit [Read error: Connection reset by peer]

03:37 RayFlower has joined #linux-rockchip

03:44 levd1 has joined #linux-rockchip

03:46 levd has quit [Ping timeout: 244 seconds]

03:53 RayFlower has quit [Read error: Connection reset by peer]

03:54 RayFlower has joined #linux-rockchip

04:13 RayFlower has quit [Read error: Connection reset by peer]

04:13 RayFlower has joined #linux-rockchip

04:23 akaizen has joined #linux-rockchip

04:23 akaizen has quit [Remote host closed the connection]

04:24 Astralix1 has joined #linux-rockchip

04:24 akaizen has joined #linux-rockchip

04:25 Astralix has quit [Ping timeout: 250 seconds]

04:34 GriefNorth has joined #linux-rockchip

04:48 levd has joined #linux-rockchip

04:50 levd1 has quit [Ping timeout: 255 seconds]

05:11 levd1 has joined #linux-rockchip

05:13 levd has quit [Ping timeout: 250 seconds]

05:26 Tony_ has joined #linux-rockchip

05:33 naobsd has joined #linux-rockchip

05:48 levd has joined #linux-rockchip

05:50 levd1 has quit [Ping timeout: 240 seconds]

06:01 RayFlower has quit [Read error: Connection reset by peer]

06:01 RayFlower has joined #linux-rockchip

06:04 Bludot has quit [Quit: Connection closed for inactivity]

06:12 RayFlower has quit [Read error: Connection reset by peer]

06:12 RayFlower has joined #linux-rockchip

06:25 levd1 has joined #linux-rockchip

06:27 levd has quit [Ping timeout: 255 seconds]

06:35 lautriv has left #linux-rockchip ["Leaving"]

06:39 RayFlower has quit [Read error: Connection reset by peer]

06:40 RayFlower has joined #linux-rockchip

06:44 levd has joined #linux-rockchip

06:46 levd1 has quit [Ping timeout: 245 seconds]

06:56 Tony_ has quit [Quit: Leaving]

07:13 RayFlower has quit [Read error: Connection reset by peer]

07:14 RayFlower has joined #linux-rockchip

07:22 Tony_ has joined #linux-rockchip

07:23 <Tony_> Hello everybody.

07:24 <Tony_> I want to replace rk616 with THC63LVD827.

07:24 <Tony_> Need I add some driver to kernel ?

07:24 <Tony_> RGB -> LVDS.

07:31 antoinemaillard has joined #linux-rockchip

07:32 levd1 has joined #linux-rockchip

07:34 levd has quit [Ping timeout: 245 seconds]

07:42 levd has joined #linux-rockchip

07:44 RayFlower has quit [Read error: Connection reset by peer]

07:44 levd1 has quit [Ping timeout: 258 seconds]

07:44 RayFlower has joined #linux-rockchip

07:54 dlezcano has joined #linux-rockchip

07:56 RayFlower has quit [Read error: Connection reset by peer]

07:57 RayFlower has joined #linux-rockchip

08:01 levd1 has joined #linux-rockchip

08:03 levd has quit [Ping timeout: 264 seconds]

08:05 dlezcano has quit [Remote host closed the connection]

08:07 RayFlower has quit [Read error: Connection reset by peer]

08:08 RayFlower has joined #linux-rockchip

08:17 levd has joined #linux-rockchip

08:20 levd1 has quit [Ping timeout: 265 seconds]

08:24 mrcan has quit [Remote host closed the connection]

08:29 <rperier> hi all

08:33 gb_master has joined #linux-rockchip

08:33 <gb_master> hello, could somebody here share a stable mainline kernel config? thanks

08:36 levd1 has joined #linux-rockchip

08:39 levd has quit [Ping timeout: 264 seconds]

08:48 gb_master has quit [Ping timeout: 246 seconds]

08:51 dlezcano has joined #linux-rockchip

08:51 RayFlower has quit [Read error: Connection reset by peer]

08:52 RayFlower has joined #linux-rockchip

08:54 levd has joined #linux-rockchip

08:55 levd1 has quit [Ping timeout: 265 seconds]

08:59 <rperier> https://github.com/mmind/linux-rockchip/blob/devel/workbench/arch/arm/configs/rk30_rk31_defconfig

08:59 <rperier> or

08:59 <rperier> https://github.com/neo-technologies/meta-rockchip/blob/mainline/recipes-kernel/linux/linux/defconfig

08:59 <rperier> but I think that the first one is better because it does not need to be modified (the second one boot from the network so you would need to change cmdline)

09:00 <rperier> arrfff , he is disconnected ^^

09:01 <Tony_> :)

09:15 levd1 has joined #linux-rockchip

09:17 levd has quit [Ping timeout: 264 seconds]

09:32 RayFlower has quit [Read error: Connection reset by peer]

09:32 RayFlower has joined #linux-rockchip

09:34 levd has joined #linux-rockchip

09:35 dlezcano has quit [Ping timeout: 264 seconds]

09:36 levd1 has quit [Ping timeout: 265 seconds]

09:37 dlezcano has joined #linux-rockchip

09:46 nighty^ has joined #linux-rockchip

09:54 levd1 has joined #linux-rockchip

09:56 wildea01 has joined #linux-rockchip

09:56 levd has quit [Ping timeout: 240 seconds]

09:57 gb_master has joined #linux-rockchip

09:58 <gb_master> thanks rperier

09:59 <gb_master> btw, mainline doesn't read the parameters partition at all?

10:00 akaizen has quit []

10:01 <rperier> no because the parameter partition is read by the bootloader and not the kernel...

10:01 <gb_master> the problem is that I'm trying with different kernel confs, but I always end up with freezes after a while... even using http://rockchip.fr/radxa/linux/rockchip_defconfig

10:01 GriefNorth has quit [Quit: WeeChat 1.0.1]

10:02 <rperier> which board ?

10:02 <gb_master> RR pro

10:03 <rperier> what kernel do you use ? could you be more precise about "with freezes after a while" ? (no logs ?)

10:03 <rperier> a release or linux-next ?

10:03 <gb_master> mainline kernel... so 3.18-rc5, I think

10:03 <gb_master> linux-next

10:04 <gb_master> after a while, the LEDs stay still, and that means that the board doesn'r reply anymore

10:04 <gb_master> probably a kernel crash

10:04 <gb_master> didn't have the chance to test the serial if logs are generated in the dmesg

10:04 <gb_master> I probably will in the weekend

10:05 <rperier> torvalds's repo is the future linux 3.18 when linux next and linux 3.19 (http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git)

10:05 <gb_master> yes that one

10:05 <rperier> s/and/is/

10:05 <gb_master> I don't even know if kernel crashes are dumped in dmesg

10:05 <rperier> you still have not a usb serial ? :/

10:06 <rperier> that's hard to understand what happens

10:06 <gb_master> it's arriving on mail today/tomorrow

10:06 <rperier> ok cool

10:06 <gb_master> dp you have RR pro?

10:07 <rperier> did not test with lastest linux-next (lastest tag) on my RR late 2013, I will test this evening just to be sure that there is no regressions

10:07 <gb_master> good

10:07 GriefNorth has joined #linux-rockchip

10:07 <rperier> (because RR pro and RR late 2013 share the same hw base except the few added extensions)

10:08 <gb_master> I will let you know when the usb serial arrives at home

10:08 <rperier> so if you use rk3188-radxarock.dts for you RR pro... I would say that it should just work fine

10:08 <gb_master> yes, I use that one

10:08 <rperier> (the added extensions won't work but that's normal)

10:09 Tony_ has quit [Read error: Connection reset by peer]

10:09 <gb_master> do you remember which tag are you using?

10:10 <rperier> gb_master: how do you use your board actually ? from ssh ?

10:10 <gb_master> yes

10:10 <rperier> it might be a panic from ethernet...

10:10 <rperier> :)

10:10 <gb_master> maybe

10:10 <rperier> I have the same issues sometimes (my rootfs is loaded from the network through NFS)

10:10 <gb_master> is the eth driver unstable?

10:10 <gb_master> ah

10:11 <rperier> and sometimes my kernel freezes because the ethernet drives does crap

10:11 <rperier> it works well most of the time but does not sometimes, I need to fix it

10:11 <rperier> which might explain your problem

10:11 <gb_master> I would totally like to contribute, as I'm a sw developer, but I guess I need the usb serial first

10:11 <rperier> yes

10:12 <karlp> it will be _very_ sanity preserving and save an incredible amount of time

10:12 <rperier> do you boot from an sdcard ?

10:12 <rperier> or an usb key

10:12 <gb_master> sdcard

10:12 <gb_master> everything's on SD

10:12 <rperier> did you try to look your system logs ?

10:12 <gb_master> I looked at dmesg logs

10:12 <gb_master> and there was nothing, at least on /var/log/dmesg

10:13 <gb_master> I guess, after a kernel panic, nothing's written on SD

10:13 <rperier> the kernel does not have time to save some logs if it crashes (it happens sometimes)

10:13 <gb_master> yes

10:13 <gb_master> I'll definitely know more in the weekend

10:13 <rperier> yes

10:14 <gb_master> do you use ubuntu?

10:14 <rperier> no I use yocto/oe

10:14 <rperier> (I build my own distro for my needs)

10:15 <gb_master> I use gentoo and I was experiencing the issue, with mainline kernel, to not be able to run non-root processes

10:15 <gb_master> even with debian, I had issues

10:15 <rperier> I don't like to use distro oriented desktop/server to do embedded things

10:15 <gb_master> FYI, I found the solution in http://www.plugcomputer.org/plugforum/index.php?topic=4879.0

10:16 <gb_master> and that setting is OK in the radxa-stable-3.0 kernel, but not in the rockchip_defconfig configuration

10:16 <rperier> I have an idea

10:16 <rperier> could you use wifi instead of ethernet

10:16 <rperier> with ssh

10:16 <gb_master> mmm

10:16 <rperier> (disable ethernet driver completly)

10:16 <gb_master> I will, as soon as I get back home

10:16 <rperier> and restart with wifi

10:16 <gb_master> didn't think of that

10:17 <rperier> :)

10:17 <gb_master> wifi is OK on mainline?

10:18 <rperier> yes it should, don't forget the firmware

10:18 <rperier> it is found on my board, did not try it

10:18 <rperier> but it should

10:19 <gb_master> thank you very much :)

10:19 <gb_master> I really hope I will be able to help you in the linux dev

10:25 RayFlower has quit [Read error: Connection reset by peer]

10:25 RayFlower has joined #linux-rockchip

10:29 dlezcano has quit [Ping timeout: 250 seconds]

10:29 dlezcano has joined #linux-rockchip

10:35 dlezcano has quit [Ping timeout: 272 seconds]

10:36 dlezcano has joined #linux-rockchip

10:38 RayFlower has quit [Read error: Connection reset by peer]

10:39 RayFlower has joined #linux-rockchip

10:41 RayFlower has quit [Read error: Connection reset by peer]

10:42 RayFlower has joined #linux-rockchip

10:51 levd1 has quit [Ping timeout: 264 seconds]

11:10 cnxsoft has quit [Ping timeout: 255 seconds]

11:17 <naobsd> many mails on linux-rockchip ml...

11:24 naobsd has quit [Quit: Page closed]

11:38 bengal has joined #linux-rockchip

11:40 c0d3z3r0 has quit [Ping timeout: 240 seconds]

11:41 c0d3z3r0 has joined #linux-rockchip

11:49 dlezcano has quit [Ping timeout: 272 seconds]

11:50 dlezcano has joined #linux-rockchip

11:55 dlezcano has quit [Ping timeout: 255 seconds]

11:55 dlezcano has joined #linux-rockchip

12:10 RayFlower has quit [Read error: Connection reset by peer]

12:10 RayFlower has joined #linux-rockchip

12:16 bengal has quit [Quit: Leaving]

12:24 RayFlower has quit [Read error: Connection reset by peer]

12:24 RayFlower has joined #linux-rockchip

12:29 RayFlower has quit [Read error: Connection reset by peer]

12:29 RayFlower has joined #linux-rockchip

12:35 dlezcano has quit [Ping timeout: 240 seconds]

12:35 dlezcano has joined #linux-rockchip

12:41 dlezcano has quit [Ping timeout: 244 seconds]

12:41 dlezcano has joined #linux-rockchip

12:55 RayFlower has quit [Read error: Connection reset by peer]

12:55 RayFlower has joined #linux-rockchip

13:07 dlezcano has quit [Ping timeout: 265 seconds]

13:07 RayFlower has quit [Read error: Connection reset by peer]

13:07 dlezcano has joined #linux-rockchip

13:07 RayFlower has joined #linux-rockchip

13:11 gb_master has quit [Quit: Page closed]

13:25 <rperier> ironic point of view: "guys please merge this patch because compat is broken" --> no feedbacks then, then 3 weeks later -> "oh my god a commit is in next and breaks compatibility. What I suggested 3 weeks ago for naming is completly wrong, it would be nice to change the name *again*" :D

13:26 <rperier> except the troll in the discussion people don't remember anything apparently

13:27 <rperier> well, until the broken thing does not go into the Linus's tree, that's a good point

13:27 cnxsoft has joined #linux-rockchip

13:27 <rperier> (the important thing being try to find a solution)

13:38 <rperier> anyway, I am just kidding, but this is a strange situation, probably because there were communication issues :)

13:40 <rperier> being from a different culture does not help, sometimes you try to find words or sentence to explain what you have in mind to a native person, that's not so easy

13:40 dlezcano has quit [Ping timeout: 265 seconds]

13:40 dlezcano has joined #linux-rockchip

13:48 GriefNorth has quit [Quit: WeeChat 1.0.1]

13:49 naobsd has joined #linux-rockchip

13:56 RayFlower has quit [Read error: Connection reset by peer]

13:56 RayFlower has joined #linux-rockchip

14:16 killbit has quit [Ping timeout: 272 seconds]

14:16 lioka has quit [Ping timeout: 272 seconds]

14:16 killbit has joined #linux-rockchip

14:17 lioka has joined #linux-rockchip

14:21 RayFlower has quit [Read error: Connection reset by peer]

14:21 RayFlower has joined #linux-rockchip

14:21 dlezcano has quit [Ping timeout: 272 seconds]

14:24 dlezcano has joined #linux-rockchip

14:26 lioka has quit [Ping timeout: 258 seconds]

14:26 lioka has joined #linux-rockchip

14:28 RayFlower has quit [Read error: Connection reset by peer]

14:28 RayFlower has joined #linux-rockchip

14:33 lioka has joined #linux-rockchip

14:33 lioka has quit [Changing host]

14:45 dlezcano has quit [Ping timeout: 255 seconds]

14:45 dlezcano has joined #linux-rockchip

14:51 dlezcano has quit [Ping timeout: 250 seconds]

14:51 dlezcano has joined #linux-rockchip

14:53 cnxsoft has quit [Quit: cnxsoft]

15:24 RayFlower has quit [Read error: Connection reset by peer]

15:25 dlezcano has quit [Ping timeout: 264 seconds]

15:25 RayFlower has joined #linux-rockchip

15:35 RayFlower has quit [Read error: Connection reset by peer]

15:35 RayFlower has joined #linux-rockchip

15:37 RayFlower has quit [Read error: Connection reset by peer]

15:37 ganbold_ has quit [Remote host closed the connection]

15:38 RayFlower has joined #linux-rockchip

15:42 FreezingCold has quit [Ping timeout: 256 seconds]

15:46 ganbold_ has joined #linux-rockchip

15:48 RayFlower has quit [Read error: Connection reset by peer]

15:49 RayFlower has joined #linux-rockchip

16:03 RayFlower has quit [Read error: Connection reset by peer]

16:03 RayFlower has joined #linux-rockchip

16:22 Abhisit has joined #linux-rockchip

16:28 <Abhisit> Do you know, what is hardware folating point unit of RK3288? I see in Rockchip RK3288 datasheet V1.0 20140516, it is VFPv3 + NEON, but I see Cortex-A17 information on ARM website, it is VFPv4 + NEON. Some can tell me, what is exactly hardware floating point on RK3288?

16:32 FreezingCold has joined #linux-rockchip

17:09 RayFlower has quit [Read error: Connection reset by peer]

17:09 RayFlower has joined #linux-rockchip

17:12 FreezingCold has quit [Ping timeout: 245 seconds]

17:18 <khilman> mmind00_: FYI: rk3288-evb boot failure in linux-next, multi_v7_defconfig + CONFIG_ARM_LPAE=y

17:18 <khilman> http://storage.armcloud.us/kernel-ci/next/next-20141121/arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y/boot-rk3288-evb-rk808.html

17:18 <khilman> bisecting now

17:18 <khilman> vanilla multi_v7_defconfig booted fine

17:22 <Abhisit> Some know, what is floating-point hardware of RK3288?

17:28 wildea01 has quit [Quit: leaving]

17:31 <mmind00_> khilman: sent an email concerning this ... I think your first try was just lucky

17:31 antoinemaillard has quit [Ping timeout: 250 seconds]

17:45 <karlp> Abhisit: I would suspect that the docs are wrong, and were copied from somewhere else,

17:45 <karlp> what are you working on that this is so important?

17:46 <Abhisit> I would like a toolchain for RK3288. It is important for me.

17:47 <Abhisit> I would like to make a toolchain for RK3288.

17:54 RayFlower has quit [Read error: Connection reset by peer]

17:55 RayFlower has joined #linux-rockchip

17:58 <Abhisit> karlp: Are you here? I really to know please, what is floating-point hardware of RK3288? Because I heed to get best performance of RK3288.

18:00 <karlp> so, given rockchips docs, who do you think is telling the truth, arm about their own core, or rockchip summarizing for some documents about a block they laid down?

18:01 paavalan has quit [Ping timeout: 264 seconds]

18:04 <Abhisit> karlp: I don't know, but Rockchip's document look link copy from RK3188, It is might be wrong.

18:05 <karlp> yes. exactly.

18:05 <karlp> so.... what's the problem?

18:07 <Abhisit> karlp: I heed to get best performance of RK3288, so I must be make correct tool chain for RK3288.

18:17 <Abhisit> karlp: If you don't know, you are welcome. Thanks.

18:27 gb_master has joined #linux-rockchip

18:27 <khilman> mmind00_: so what changed upstream to start seeing these now?

18:28 <mmind00_> khilman: smp support landed

18:29 <khilman> mmind00_: ah, ok. makes sense. thx

18:30 <mmind00_> khilman: i.e. the problem are the not-initialized cntvoff registers not being initialized correctly ... you can see that in your log by the jumping log time indices

18:32 <khilman> yeah, ok

18:52 gb_master has quit [Ping timeout: 258 seconds]

18:59 RayFlower has quit [Read error: Connection reset by peer]

19:00 RayFlower has joined #linux-rockchip

19:11 gb_master has joined #linux-rockchip

19:20 RayFlower has quit [Read error: Connection reset by peer]

19:21 RayFlower has joined #linux-rockchip

19:21 gb_master has quit [Ping timeout: 265 seconds]

19:23 bengal has joined #linux-rockchip

19:23 rz2k has joined #linux-rockchip

19:39 gb_master has joined #linux-rockchip

19:40 <gb_master> @rperier, it was the eth driver, you were right

19:40 <gb_master> it's not crashing anymore

19:41 FreezingCold has joined #linux-rockchip

19:43 mrcan has joined #linux-rockchip

20:02 gb_master has quit [Remote host closed the connection]

20:18 FreezingCold has quit [Remote host closed the connection]

20:21 Abhisit has quit [Quit: Page closed]

20:31 FreezingCold has joined #linux-rockchip

20:36 mmind00_ is now known as mmind00

20:57 RayFlower has quit [Read error: Connection reset by peer]

20:58 RayFlower has joined #linux-rockchip

21:11 FreezingCold has quit [Remote host closed the connection]

21:29 nighty^ has quit [Quit: Disappears in a puff of smoke]

21:30 <rperier> mmind00: what are the gpio-leds "green", "yellow" and "sleep" exactly on RR?

21:31 <rperier> I am fixing an issue, we have a backtrace at boot because the leds-gpio driver tries to create null sysfs interface , intel recently switched from of to fwnode API which introduced a regression about the name used for the sysfs file

21:32 <rperier> a solution would be to add a "label" property to these gpio-leds node, this is why I was wondering what are these leds exactly

21:34 <mmind00> rperier: my radxa has a green, yellow and red led ... the red one is labeled "sleep" in the schematics ...

21:35 <mmind00> rperier: it also looks like they call the green one "state1" and the yellow one "state2" in the schematics

21:35 <rperier> mhh yeah, just find it

21:36 <rperier> it seems that we recent changes in leds-gpio, the property "label" is no longer optional :)

21:36 <rperier> s/we/with/

21:37 <mmind00> which would make it a regression ... normally you are not allowed to break on older devicetrees

21:38 <rperier> yes

21:39 <rperier> so a real solution... would be try to load the device_node name as before... but I don't know it it does make sense with fwnode API

21:39 <rperier> (in order to revert backward compat)

21:40 <mmind00> or in our case just add the labels :-) ... we don't have devicetrees on actual devices, so we could take the easy way out

21:43 <rperier> yes but the driver itself is still wrong as it breaks compat, no ?

21:44 <mmind00> rperier: correct

21:48 <rperier> problem fixed :)

21:51 <rperier> I will send a patch to add these label to rk3188-radxarock.dts and send an email to the developers to explain the problem (leds-gpio)

21:52 rz2k has quit []

22:17 bengal has quit [Read error: Connection reset by peer]

22:17 bengal has joined #linux-rockchip

22:24 RayFlower has quit [Read error: Connection reset by peer]

22:24 RayFlower has joined #linux-rockchip

22:26 RayFlower has quit [Read error: Connection reset by peer]

22:27 FreezingCold has joined #linux-rockchip

22:27 RayFlower has joined #linux-rockchip

22:50 RayFlower has quit [Read error: Connection reset by peer]

22:50 RayFlower has joined #linux-rockchip

23:03 bengal has quit [Quit: Leaving]

23:18 RayFlower has quit [Read error: Connection reset by peer]

23:19 RayFlower has joined #linux-rockchip

23:24 nighty^ has joined #linux-rockchip

23:31 npcomp_ is now known as npcomp

23:36 RayFlower has quit [Read error: Connection reset by peer]

23:36 RayFlower has joined #linux-rockchip

23:42 RayFlower has quit [Read error: Connection reset by peer]

23:43 RayFlower has joined #linux-rockchip

23:51 RayFlower has quit [Read error: Connection reset by peer]

23:52 RayFlower has joined #linux-rockchip

23:58 RayFlower has quit [Read error: Connection reset by peer]

23:59 RayFlower has joined #linux-rockchip