#linux-rockchip on 2016-03-16 — 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:17 <mmind00> although I also don't see anything helpful there ... that nice status register seems to have appeared in the newer socs

00:33 <bryanp_> Looks like boot mode register might be telling enough for me but not 100%. As long as I can rule out that we called a restart or the kernel did for some reason the status of 6 should specify a watchdog reboot

00:47 levd has joined #linux-rockchip

00:59 hipboi has joined #linux-rockchip

01:00 hipboi has quit [Client Quit]

01:06 levd1 has joined #linux-rockchip

01:08 levd has quit [Ping timeout: 244 seconds]

01:08 levd1 is now known as levd

01:42 levd1 has joined #linux-rockchip

01:45 levd has quit [Ping timeout: 276 seconds]

01:45 levd1 is now known as levd

02:03 cnxsoft has joined #linux-rockchip

02:11 c0d3z3r0 has quit [Ping timeout: 250 seconds]

02:11 levd1 has joined #linux-rockchip

02:11 c0d3z3r0 has joined #linux-rockchip

02:13 levd has quit [Ping timeout: 246 seconds]

02:13 levd1 is now known as levd

02:14 Sadneophyte has joined #linux-rockchip

02:20 levd1 has joined #linux-rockchip

02:22 levd has quit [Ping timeout: 250 seconds]

02:22 levd1 is now known as levd

02:30 amstan_ has joined #linux-rockchip

02:40 <Sadneophyte> I have been using alarm on a rk3288 asus c201p for a couple months now, and I was getting tired of the SDcard wait times, What are the opinions here about installing it to the eMMC? Do I need to worry about libreboot or uboot? Where can I read about the correct way to deal with all the chromeos partitions, can anyone think of a good install guide which can be adapted?

03:07 levd1 has joined #linux-rockchip

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

03:09 levd1 is now known as levd

03:13 Sadneophyte has quit [Ping timeout: 252 seconds]

03:19 levd1 has joined #linux-rockchip

03:22 levd has quit [Ping timeout: 268 seconds]

03:22 levd1 is now known as levd

03:29 Sadneophyte has joined #linux-rockchip

03:37 levd1 has joined #linux-rockchip

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

03:39 levd1 is now known as levd

03:45 levd1 has joined #linux-rockchip

03:47 levd has quit [Ping timeout: 252 seconds]

03:47 levd1 is now known as levd

03:54 levd1 has joined #linux-rockchip

03:58 levd has quit [Ping timeout: 268 seconds]

03:58 levd1 is now known as levd

03:58 Sadneophyte has quit [Ping timeout: 252 seconds]

04:07 pozzoni has quit [Ping timeout: 260 seconds]

04:07 pozzoni has joined #linux-rockchip

04:13 levd1 has joined #linux-rockchip

04:15 levd has quit [Ping timeout: 264 seconds]

04:15 levd1 is now known as levd

04:53 levd1 has joined #linux-rockchip

04:56 levd has quit [Ping timeout: 260 seconds]

04:56 levd1 is now known as levd

05:30 levd1 has joined #linux-rockchip

05:32 levd has quit [Ping timeout: 240 seconds]

05:32 levd1 is now known as levd

05:52 JohnDoe_71Rus has joined #linux-rockchip

05:56 levd1 has joined #linux-rockchip

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

05:59 levd1 is now known as levd

06:21 levd1 has joined #linux-rockchip

06:23 levd has quit [Ping timeout: 264 seconds]

06:23 levd1 is now known as levd

06:47 levd1 has joined #linux-rockchip

06:49 levd has quit [Ping timeout: 240 seconds]

06:49 levd1 is now known as levd

07:20 levd1 has joined #linux-rockchip

07:22 levd has quit [Ping timeout: 260 seconds]

07:22 levd1 is now known as levd

07:23 wadim_ has joined #linux-rockchip

07:31 amstan_ has quit [Ping timeout: 248 seconds]

07:32 amstan_ has joined #linux-rockchip

07:38 amstan_ has quit [Ping timeout: 248 seconds]

07:49 mrjay has joined #linux-rockchip

07:49 mrjay has quit [Client Quit]

07:53 levd1 has joined #linux-rockchip

07:56 levd has quit [Ping timeout: 268 seconds]

07:56 levd1 is now known as levd

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

08:24 levd has joined #linux-rockchip

08:34 levd1 has joined #linux-rockchip

08:36 levd has quit [Ping timeout: 252 seconds]

08:36 levd1 is now known as levd

08:46 levd1 has joined #linux-rockchip

08:48 levd has quit [Ping timeout: 244 seconds]

08:48 levd1 is now known as levd

08:52 levd1 has joined #linux-rockchip

08:54 levd has quit [Ping timeout: 246 seconds]

08:54 levd1 is now known as levd

09:15 cnxsoft has quit [Remote host closed the connection]

09:18 levd1 has joined #linux-rockchip

09:20 levd has quit [Ping timeout: 252 seconds]

09:20 levd1 is now known as levd

09:24 levd1 has joined #linux-rockchip

09:24 cnxsoft has joined #linux-rockchip

09:24 levd has quit [Ping timeout: 252 seconds]

09:24 levd1 is now known as levd

09:27 afaerber has joined #linux-rockchip

09:35 levd1 has joined #linux-rockchip

09:37 levd has quit [Ping timeout: 252 seconds]

09:37 levd1 is now known as levd

09:51 <afaerber> mmind00: seeing that you canceled your 4.6 pulls, do you plan to start queuing the initial GeekBox patches?

09:51 <afaerber> the whole net discussion is slowly moving towards fixes in the driver, not affecting my patches

09:53 <mmind00> afaerber: merge-window is open, so arm-soc won't take new features till rc1 ... and yep the network discussion seems pretty limited to the actual driver

09:54 <afaerber> mmind00: any other comments beyond the documentation?

09:54 <afaerber> for example, are you okay with Julien's proposed cleanups for the other boards?

09:55 <afaerber> I am hesitant to adopt that new EV code if the other boards don't

09:55 <afaerber> I don't even know how to test it

09:57 <mmind00> is anybody using that at all? :-) [just grepped through the kernel but failed to find any user of that]

09:57 <afaerber> maybe systemd or X11?

09:58 <afaerber> matthias_bgg: didn't you use evtest or something for power key testing recently? :)

09:59 <mmind00> yeah, I see some users in the input subsystem ... but it seems nobody on the devicetree side is using that currently

10:00 <matthias_bgg> afaerber, yes "evtest --grab /dev/input/eventX" should show you any event coming from the input system

10:00 <mmind00> afaerber: pcf50633-input.c even uses both EV_KEY and EV_PWR for its power-key

10:00 <mmind00> quite strange

10:02 <afaerber> matthias_bgg: do the trees you've worked with use linux,input-type = <EV_PWR> or just linux,code = <KEY_POWER>? does it make a difference anywhere?

10:07 levd1 has joined #linux-rockchip

10:09 levd has quit [Ping timeout: 260 seconds]

10:09 levd1 is now known as levd

10:12 <matthias_bgg> afaerber, do you know how to decipher the dts in proc?

10:12 <matthias_bgg> hexdump -Cv /proc/device-tree//soc@0/gpio-keys/button@1/linux\,code

10:12 <matthias_bgg> 00000000 00 00 00 74 |...t|

10:13 <afaerber> so 74 = 116 = KEY_POWER

10:18 levd has quit [Ping timeout: 244 seconds]

10:18 vev has joined #linux-rockchip

10:23 <vev> #libreidea is looking for voluntary devs to help us on idea creation tools - join us! - libreidea.org

10:28 vev has left #linux-rockchip ["Leaving"]

11:39 libv_ has joined #linux-rockchip

11:41 libv has quit [Ping timeout: 246 seconds]

12:02 libv_ is now known as libv

12:42 <afaerber> mmind00: have you noticed the /memory dtc warnings?

12:43 <afaerber> I'm wondering whether the plan is to add @0 (or @0,0 or something)

12:43 <mmind00> which warnings ... when I was compiling dtbs in my branches for 4.6 there were none

12:43 <afaerber> linux-next

12:43 <afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-evb-act8846.dtb

12:43 <afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name

12:43 <afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-geekbox.dtb

12:43 <afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-geekbox-landingship.dtb

12:43 <afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name

12:43 <afaerber> DTC arch/arm64/boot/dts/rockchip/rk3368-r88.dtb

12:43 <afaerber> Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, but no unit name

12:43 <mmind00> I remember seeing people also complain about other things the updated dtc created

12:44 <mmind00> so I guess this will get addressed before hitting mainline (hopefully)

12:44 <afaerber> well, I am wondering about whether I need to make changes to my geekbox .dts that is not yet in the tree, when sending v4

12:45 <mmind00> afaerber: the memory nodes follow the general description in the ePAPR (I'm at least 80% sure :-) )

12:46 <afaerber> mmind00: I checked booting booting-without-of.txt and that mentions @0 somewhere

12:47 <afaerber> To define the physical memory layout of your board, you should

12:47 <afaerber> create one or more memory node(s). You can either create a single

12:47 <afaerber> node with all memory ranges in its reg property, or you can create

12:47 <afaerber> several nodes, as you wish. The unit address (@ part) used for the

12:47 <afaerber> full path is the address of the first range of memory defined by a

12:47 <afaerber> given node. If you use a single memory node, this will typically be

12:47 <afaerber> @0.

12:48 <mmind00> and my memory is bad it seems ... ePAPR also has the @0

12:48 <afaerber> but then again it goes on to talk about "the /soc<SOCname> node" which we all use as just /soc too

12:49 <mmind00> I do think @0 would be the correct implementation though

12:50 <mmind00> (meaning @start-address, which is 0 on the rk3368)

12:50 <afaerber> yeah, I did check that :)

12:50 <afaerber> so... should I just adopt that for the GeekBox patch or also convert the existing boards?

13:06 JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]

13:11 cnxsoft1 has joined #linux-rockchip

13:12 bryanp_ has quit [Ping timeout: 276 seconds]

13:13 cnxsoft has quit [Ping timeout: 252 seconds]

13:13 cnxsoft1 is now known as cnxsoft

13:14 bryanp has joined #linux-rockchip

13:16 <mmind00> afaerber: however you like :-) ... if you're not doing it, I guess it will be me doing the conversion

13:30 dlezcano has quit [Quit: Leaving]

13:31 dlezcano has joined #linux-rockchip

13:43 <afaerber> mmind00: prepended it

13:44 <afaerber> I guess we don't need to backport that, so I skipped looking up Fixes headers

14:01 cnxsoft has quit [Quit: cnxsoft]

14:14 JohnDoe_71Rus has joined #linux-rockchip

15:06 afaerber has quit [Quit: Ex-Chat]

15:23 wadim_ has quit [Remote host closed the connection]

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

15:25 sunilmohan_ has joined #linux-rockchip

15:55 sunilmohan has joined #linux-rockchip

15:56 sunilmohan_ has quit [Ping timeout: 244 seconds]

16:07 matthias_bgg has quit [Ping timeout: 244 seconds]

16:12 matthias_bgg has joined #linux-rockchip

16:38 afaerber has joined #linux-rockchip

17:19 akaizen has joined #linux-rockchip

18:02 akaizen has quit [Remote host closed the connection]

18:02 akaizen has joined #linux-rockchip

18:06 ganbold has quit [Ping timeout: 244 seconds]

18:41 paulk-collins has joined #linux-rockchip

18:50 akaizen has quit [Remote host closed the connection]

18:57 afaerber has quit [Quit: Ex-Chat]

19:00 paulk-collins has quit [Read error: Connection reset by peer]

19:00 paulk-collins has joined #linux-rockchip

19:25 akaizen has joined #linux-rockchip

20:20 matthias_bgg has left #linux-rockchip ["Leaving"]

20:21 akaizen has quit [Remote host closed the connection]

20:29 vickycq has quit [Ping timeout: 246 seconds]

20:31 vickycq has joined #linux-rockchip

20:47 bbelos has quit [Ping timeout: 276 seconds]

21:10 bbelos has joined #linux-rockchip

21:14 akaizen has joined #linux-rockchip

21:15 akaizen has quit [Read error: Connection reset by peer]

21:15 akaizen has joined #linux-rockchip

21:19 JohnDoe_71Rus has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]

21:47 afaerber has joined #linux-rockchip

22:40 akaizen has quit [Remote host closed the connection]

22:52 <bryanp> Anyone here have any experience with LAN8720 and warm restart not reiniting the device properly?

23:00 <naobsd> bryanp: which board/kernel?

23:00 <bryanp> its 3.0.8+ on something sort of like a minix neo x5

23:01 <bryanp> rk3066

23:03 cosm has joined #linux-rockchip

23:06 paulk-collins has quit [Quit: Quitte]

23:07 <naobsd> hmmm less experience with that kernel... :(

23:07 <naobsd> are you using stock kernel?

23:08 <naobsd> at least you have to use the kernel configured for your board

23:10 XPLOD6K has joined #linux-rockchip

23:10 <naobsd> then you need to check emac(vmac?) driver which does phy reset properly

23:30 naobsd has quit [Remote host closed the connection]

23:31 cosm has quit [Ping timeout: 276 seconds]

23:32 naobsd has joined #linux-rockchip

23:37 linux-rockchip has quit [Remote host closed the connection]

23:39 linux-rockchip has joined #linux-rockchip

23:50 ganbold has joined #linux-rockchip

23:51 <bryanp> Whoops sorry got stuck on recovery repacking and been focused

23:51 <bryanp> I am running a kernel config'd for my board but there must be a kernel driver but. rk_29 vmac + generic phy driver

23:51 <bryanp> bug* excuse my typo

23:54 nighty-_ has quit [Remote host closed the connection]

23:58 cosm has joined #linux-rockchip